From Gabriel.CalixtodePaula at windriver.com Tue Jul 4 12:56:43 2023 From: Gabriel.CalixtodePaula at windriver.com (Calixto de Paula, Gabriel) Date: Tue, 4 Jul 2023 12:56:43 +0000 Subject: [Starlingx-discuss] Sanity and Regression - StarlingX + STX-Openstack MASTER build [20230702T060000Z] results - Jul - 02 Message-ID: Hi all, StarlingX + STX-Openstack sanity and regression results: Overall run status: GREEN Build Info: Build date: 02-Jul ISO:https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230702T060000Z/outputs/iso/starlingx-intel-x86-64-cd.iso Helm Charts:https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230702T060000Z/outputs/helm-charts/stx-openstack-1.0-1.stx.55-debian-stable-versioned.tgz AIO-DX Baremetal with VSWITCH_TYPE=OVS Sanity Results: Overall Status: GREEN Automated Test Results Summary: ------------------------------------------------------ Passed: 15 (100.00%) Failed: 0 (0.00%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS? 20230704 01:21:51?test_ssh_to_hosts PASS?? 20230704 01:23:12?test_lock_unlock_host PASS?? 20230704 01:42:20?test_openstack_services_healthy PASS?? 20230704 01:43:21?test_reapply_stx_openstack_no_change[controller-0] PASS?? 20230704 01:45:24?test_reapply_stx_openstack_no_change[controller-1] PASS?? 20230704 01:54:14?test_horizon_create_delete_instance PASS?? 20230704 01:56:52?test_swact_controllers PASS?? 20230704 02:04:23?test_ping_between_two_vms[tis-centos-guest-virtio-virtio] PASS?? 20230704 02:11:00?test_migrate_vm[tis-centos-guest-live-None] PASS?? 20230704 02:15:57?test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS?? 20230704 02:20:27?test_nova_actions[tis-centos-guest-dedicated-suspend-resume] PASS?? 20230704 02:24:50?test_evacuate_vms PASS?? 20230704 02:57:42?test_system_coredumps_and_crashes[core_dumps] PASS?? 20230704 02:57:57?test_system_coredumps_and_crashes[crash_reports] PASS?? 20230704 02:58:03?test_system_alarms ------------------------------------------------------ We'd like to point out that there is a Launchpad open for the TC test_reapply_stx_openstack_no_change[controller-1] : STX-O| config-out-of-date alarm won't disappear on controller-1 after swact and reapplying app This TC is passing on a re-run. Regression Results: Overall Status: GREEN Automated Test Results Summary: ------------------------------------------------------ Passed: 12 (100.0%) Failed: 0 (0.0%) Total Executed: 12 List of Test Cases: ------------------------------------------------------ PASS 20230704 03:03:19 test_lldp_neighbor_remote_port PASS 20230704 03:04:46 test_kernel_module_signatures PASS 20230704 03:05:47 test_delete_heat_after_swact[OS_Cinder_Volume.yaml] PASS 20230704 03:10:35 test_multiports_on_same_network_vm_actions[virtio_x4] PASS 20230704 03:30:43 test_cpu_pol_vm_actions[2-dedicated-image-volume] PASS 20230704 03:42:36 test_vm_mem_pool_default_config[2048] PASS 20230704 03:45:30 test_vm_mem_pool_default_config[1048576] PASS 20230704 03:51:46 test_resize_vm_positive[local_image-4_1_512-5_2_1024-image] PASS 20230704 03:58:46 test_server_group_boot_vms[affinity-2] PASS 20230704 04:04:01 test_server_group_boot_vms[anti_affinity-2] PASS 20230704 04:09:33 test_vm_with_config_drive PASS 20230704 04:37:45 test_lock_with_vms ----------------------------------------------------------------------- regards, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Tue Jul 4 16:46:39 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 4 Jul 2023 16:46:39 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX Networking Sub-Project Meeting (bi-weekly) Message-ID: The stx networking project meeting is cancelled for Thursday July 6 as this is a shutdown week for WR, so there is nobody to chair the meeting. Re-sending with new zoom link Bi-weekly on Thursday 0615 PT / 0915 ET Zoom Link: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-networking Networking team wiki: https://wiki.openstack.org/wiki/StarlingX/Networking -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3651 bytes Desc: not available URL: From Ghada.Khalil at windriver.com Tue Jul 4 17:44:25 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Tue, 4 Jul 2023 17:44:25 +0000 Subject: [Starlingx-discuss] TSC & Community Call - July 5/2023 -- no WR participation Message-ID: Hi Ildiko, This week is a Wind River shutdown week and all WR employees are off, so there will be no participants from WR on the TSC or Community call. Would you like to chair the calls or should we cancel for this week? Note: The call is scheduled for the Asia Friendly zone this week. Thanks, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openstack.org Tue Jul 4 17:51:17 2023 From: ildiko at openstack.org (Ildiko Vancsa) Date: Tue, 4 Jul 2023 10:51:17 -0700 Subject: [Starlingx-discuss] TSC & Community Call - July 5/2023 -- no WR participation In-Reply-To: References: Message-ID: Hi Ghada, Thank you for reaching out. Greg brought up the topic on the Community Call last week and I thought we agreed to cancel this week?s call. I will probably be able to dial in, but I will not be able to host the call tomorrow as I will be in a louder environment at that time. In that sense, I think it?s probably better if we officially cancel it, and I will try to join and catch anyone who didn?t see the emails. Would that work? Thanks, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 4, 2023, at 10:44, Khalil, Ghada wrote: > > Hi Ildiko, > This week is a Wind River shutdown week and all WR employees are off, so there will be no participants from WR on the TSC or Community call. > > Would you like to chair the calls or should we cancel for this week? > > Note: The call is scheduled for the Asia Friendly zone this week. > > > Thanks, > Ghada From ThalesElero.Cervi at windriver.com Tue Jul 4 18:17:24 2023 From: ThalesElero.Cervi at windriver.com (Cervi, Thales Elero) Date: Tue, 4 Jul 2023 18:17:24 +0000 Subject: [Starlingx-discuss] Minutes: OpenStack Distro Team Call (Jul 04, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-distro-openstack-meetings Minutes from the OpenStack Distro team call Jul 04, 2023 Build: - Build Issues: None Installation: - Installation Issues: None Sanity with stx-openstack (main branch): - Last Successful Execution: (OVS) Tue Jul 04 12:39:12 UTC 2023 - Overall status: GREEN ??????Sanity - Passed: 15 (100.00%) | Failed: 0 (0.0%) ??????Regression - Passed: 12 (100.00%) | Failed: 0 (0.0%) - Bugs Affecting Weekly Sanity/Regression: - No Reproducible bugs currently open. Only intermittent issues # LP 2023657: STX-O| config-out-of-date alarm won't disappear on controller-1 after swact and reapplying app # LP 2012389: STX-Openstack: Failed to activate binding for port for live migration # LP 2007303: STX-Openstack: "nova live-migration" fails to live migrate after host is forcefully turned off/on - StarlingX 9.0 Release: - Storyboard/Tasks for containerizing OpenStack clients: https://storyboard.openstack.org/#!/story/2010797 - In progress - Storyboard/Tasks for OpenStack upversion (Antelope): https://storyboard.openstack.org/#!/story/2010715 - In progress - We need the platform/application manifest decoupling to finish this work - Locally building the packages we faced an issue with required build dependencies that are higher than our current debian-bullseye.lst entries (e.g. oslo-db, sqlalchemy, keystone-auth) - Storyboard/Tasks for decoupling platform and application manifests: https://storyboard.openstack.org/#!/story/2010797 - Infra team is prioritizing the CENGN decommission and will act on it after that General Topics: - OVS-DPDK support on Debian: # LP 2008124: DPDK support check broken with OVS-DPDK on Debian - Waiting on Code Review # (new) LP 2025682: OVS-DPDK installation failing on Debian - Backlog -- Best Regards, Thales Cervi -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bruno.Muniz at encora.com Tue Jul 4 19:17:04 2023 From: Bruno.Muniz at encora.com (Bruno Drugowick Muniz) Date: Tue, 4 Jul 2023 19:17:04 +0000 Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization In-Reply-To: References: Message-ID: Hello, Mitch. * "Please let me know I should follow a particular procedure. Otherwise I intend to create a story in storyboard." I believe that's the way to go. Just so you know, for the work under the /virtualbox directory of the same repository, we used the original story with the Task that merged the code back in 2019, adding new Tasks to it. Regarding the "Install StarlingX Kubernetes in a virtual environment" page, you might want to look at what we're proposing at https://review.opendev.org/c/starlingx/docs/+/886178. Basically, for now, we don't remove all the detailed procedures but provide an additional "automated install" guide at the top. Regards, Bruno. ________________________________ From: Thebeau, Michel Sent: Wednesday, June 28, 2023 16:50 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization You don't often get email from michel.thebeau 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. Hi, I prepared the following description of enhancements I intend towards the libvirt virtual deployment method. Please let me know I should follow a particular procedure. Otherwise I intend to create a story in storyboard. Mitch. === Starlingx Libvirt deployment method host utilization enhancements References: "Install StarlingX Kubernetes in a virtual environment" - https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html#index-install-r7-8966076f0e81 Libvirt deployment method in starlingx/tools - https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt Libvirt deployment method moved this week to starlingx/virtual-deployment - https://opendev.org/starlingx/virtual-deployment/src/branch/master/libvirt Motivation is to: A) maintain attributes for more than one virtual lab B) improve the usage and selection of the host's resources for disk, memory and cpu C) isolate cluster networks where more than one virtual lab may be running Philosophy of continuity: Introduce changes and developments in continuity with established examples and approaches. - Maintain the existing examples for default setting and the 'mad' override. - Establish regression test based on the default setting and 'mad' override to ensure that a user of the deployment method can continue to do the same thing they used to do. - Maintain and extend the use of overridable variable definitions for the attributes of a lab. - Maintain and extend the use of command line parameters for configuration selection, such as "-c 'simplex'". - Maintain and extend the existing workflow: "exporting variables, setup_network.sh, setup_configation.sh, destroy_configuration.sh, destroy_network.sh". A) Maintain configurations for more than one virtual cluster: Motivation: allow a lab's attributes to be recalled from a configuration file and operate upon that lab specifically. Establish a precedent for a configuration file used to override the default attributes. Refer to the README.rst "Overview" section which lists environment variables CONTROLLER, WORKER, BRIDGE_INTERFACE, EXTERNAL_NETWORK, EXTERNAL_IP. Provide a default configuration file that will reset the variables to defaults as they currently exist within the deployment/libvirt scripts, including: BRIDGE_INTERFACE=${BRIDGE_INTERFACE:-stxbr} EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} CONFIGURATION=${CONFIGURATION:-simplex} CONTROLLER=${CONTROLLER:-controller} WORKER=${WORKER:-worker} STORAGE=${STORAGE:-storage} WORKER_NODES_NUMBER=${WORKER_NODES_NUMBER:-1} STORAGE_NODES_NUMBER=${STORAGE_NODES_NUMBER:-1} Provide an example configuration file that sets a lab's attributes deviating from the default. Especially, the default and the example should co-exist. Consider honouring the "mad" example in README.rst. If necessary provide an option to select values, or a script to set variables, from that configuration file. B) Improve usage and selection of host's resources: Motivation: allow lab specific attributes for the host's resources and provide tools to inspect those resources within the contexts of the virtual labs and/or overall Note: Ensure that all changes are providing defaults that are equivalent to the existing implementation. Values to add to the lab's attributes: Add DOMAIN_DIRECTORY to the set of overridable variables Add an override variable for the DISK file location for each node in a virtual lab. (currently hardcoded /var/lib/libvirt/images in functions.sh) Add an override variable for the MEMORY setting for each node (currently XML hardcoded ) Add an override variable for the CPU setting of each node (currently XML hardcoded ) Add scripting to assist with supervising the host's resources, such as: - listing the lab's nodes and networks; - inspecting the lab's network configurations; - inspecting the host's and lab's disk usage per configured disk; - listing a lab's nodes' cpu and memory allocations C) Isolate cluster networks where more than one cluster may be running: Motivation: on a host that has a capacity to run virtual clusters, ensure that there is no networking crosstalk between the running clusters. Provide scripting to add/remove iptables restrictions for a lab's networks. Initially assume no inter-cluster communication, and only the OAM network will route to external networks. Include: - ipv4 and/or ipv6 - a lab specific iptables CHAIN Probably: omit running this script automatically, since it changes the deployment behaviour. Consider adding an optional parameter to setup_network.sh. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Jul 5 00:29:57 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 5 Jul 2023 00:29:57 +0000 Subject: [Starlingx-discuss] TSC & Community Call - July 5/2023 -- no WR participation In-Reply-To: References: Message-ID: Hi Ildiko, I agree that canceling seems to be the best option. Thanks, Ghada -----Original Message----- From: Ildiko Vancsa Sent: Tuesday, July 4, 2023 1:51 PM To: Khalil, Ghada Cc: starlingx-discuss at lists.starlingx.io Subject: Re: TSC & Community Call - July 5/2023 -- no WR participation CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Ghada, Thank you for reaching out. Greg brought up the topic on the Community Call last week and I thought we agreed to cancel this week?s call. I will probably be able to dial in, but I will not be able to host the call tomorrow as I will be in a louder environment at that time. In that sense, I think it?s probably better if we officially cancel it, and I will try to join and catch anyone who didn?t see the emails. Would that work? Thanks, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 4, 2023, at 10:44, Khalil, Ghada wrote: > > Hi Ildiko, > This week is a Wind River shutdown week and all WR employees are off, so there will be no participants from WR on the TSC or Community call. > > Would you like to chair the calls or should we cancel for this week? > > Note: The call is scheduled for the Asia Friendly zone this week. > > > Thanks, > Ghada From Ghada.Khalil at windriver.com Wed Jul 5 00:30:58 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 5 Jul 2023 00:30:58 +0000 Subject: [Starlingx-discuss] Canceled: StarlingX TSC & Community Call [APAC Friendly Time] Message-ID: Cancelled for Wednesday July 5. As discussed in recent community meetings, we will be meeting once a month (first Wednesday) at 7pm PDT/ 10pm EDT / +1 10am CST https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1836 bytes Desc: not available URL: From openinfradn at gmail.com Wed Jul 5 04:42:33 2023 From: openinfradn at gmail.com (open infra) Date: Wed, 5 Jul 2023 10:12:33 +0530 Subject: [Starlingx-discuss] Community Communication Channels In-Reply-To: References: Message-ID: CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord. Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply). On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa wrote: > Hi StarlingX Community, > > I?m reaching out to you about a recurring topic that came up during the > PTG last week again. > > While the community is actively using the mailing list, it is not always > the best platform, as it doesn?t allow for more synchronous chat. > Contributors at the event had a growing interest in finding a way to > provide the opportunity for more synchronous communication to capture the > project teams? chatters, and enable newcomers to reach out and start to > participate. > > Challenges: > * Tooling: People raised that while it is an open protocol, IRC still > doesn?t feel inclusive due to its simplicity. > * Format: The current one-channel setup doesn?t feel efficient and > comfortable, since people need to address everyone in the channel with > every topic they have a question or comment about. > > > Proposal to move forward: > * Tooling: The preferred tool in last week?s conversation was Matrix - > https://matrix.org > - It is an open tool, which ensures continued access to the platform > and its features > - It is more modern than IRC > > * Format: The idea came up to create multiple channels for the StarlingX > project > - We can keep the all-community channel > - We can create channels for each project team, that are more topic > specific > - We also have the option to create a channel for newcomers, which > could include troubleshooting type of conversations as well > > > In order to identify next steps, please share your feedback about the > proposal above. Ie: What do you think about Matrix? Would you be more > comfortable using a chat tool with the more fine grained configuration of > having multiple channels? > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Director of Community > Open Infrastructure Foundation > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > -------------- next part -------------- An HTML attachment was scrubbed... URL: From openinfradn at gmail.com Wed Jul 5 10:02:05 2023 From: openinfradn at gmail.com (open infra) Date: Wed, 5 Jul 2023 15:32:05 +0530 Subject: [Starlingx-discuss] How to get standby controller as active after active controller down Message-ID: Hi, In a stx standard dedicated storage setup, active controller was down (disk failure). Now I need to get the stand by controller as the active controller (in order to get the failed controller up and running). swatc is required to run in an active controller. So, how to make stand by as the active controller itself? Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Wed Jul 5 18:01:13 2023 From: Robert.Church at windriver.com (Church, Robert) Date: Wed, 5 Jul 2023 18:01:13 +0000 Subject: [Starlingx-discuss] proposal to add Jim Gauld for core reviewer in the "config" repo In-Reply-To: References: Message-ID: +1 From: Chris Friesen Date: Tuesday, July 4, 2023 at 11:53 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] proposal to add Jim Gauld for core reviewer in the "config" repo Jim Gauld has been around for a long time and has a deep historical knowledge of the StarlingX project. He has been dealing with quite a few issues in the config repo, mostly related to Kubernetes issues and upgrades and has an excellent understanding of how the pieces fit together. As such, I'd like to propose Jim as an addition to the core reviewer list for the config repo. Thanks, Chris _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Wed Jul 5 18:20:27 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 5 Jul 2023 11:20:27 -0700 Subject: [Starlingx-discuss] TSC & Community Call is canceled this week Message-ID: <18E0DDAC-C09D-4EA4-A789-2C293F38A072@openinfra.dev> Hi StarlingX Community, It is a friendly reminder that the TSC & Community Call is canceled this week, as many of the project?s contributors are not available for the call. If you have any topics that you would like to discuss, please bring them up on the mailing list, or the project?s IRC channel, which is #starlingx at the OFTC network. The next call will happen next Wednesday (July 12) at 7am PST. You can find more details about the calls here: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation From Greg.Waines at windriver.com Mon Jul 10 12:24:17 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 10 Jul 2023 12:24:17 +0000 Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization In-Reply-To: References: Message-ID: Hey Mich, Thanksfor looking at this. Do you intent to update the virtual install guides as well ? ... as part of this work ? e.g. https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_install_kubernetes.html A heads up if you do ... (I think I've mentioned this a couple of times) * The bare-metal install guides have been enhanced/updated and maintained over the last few stx releases * ... but the virtual install guides have not * E.g. if you compare * https://docs.starlingx.io/deploy_install_guides/release/bare_metal/aio_simplex_install_kubernetes.html * And * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex.html * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_environ.html * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_install_kubernetes.html you'll see several differences that are not necessarily due virtual versus bare-metal. * We (doc team) did not maintain the virtual install guides because we were thinking that * It was too much overhead maintaining both guides, * Instead we were going to combine the guides * And just have in the very few places, the difference between virtual versus bare-metal * BUT ... we have not had time to look at this. * * If you are interested in doing this ... let me, Juanita and Ron know and we can provide some guidance here. Greg. From: Thebeau, Michel Sent: Wednesday, June 28, 2023 3:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Hi, I prepared the following description of enhancements I intend towards the libvirt virtual deployment method. Please let me know I should follow a particular procedure. Otherwise I intend to create a story in storyboard. Mitch. === Starlingx Libvirt deployment method host utilization enhancements References: "Install StarlingX Kubernetes in a virtual environment" - https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html#index-install-r7-8966076f0e81 Libvirt deployment method in starlingx/tools - https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt Libvirt deployment method moved this week to starlingx/virtual-deployment - https://opendev.org/starlingx/virtual-deployment/src/branch/master/libvirt Motivation is to: A) maintain attributes for more than one virtual lab B) improve the usage and selection of the host's resources for disk, memory and cpu C) isolate cluster networks where more than one virtual lab may be running Philosophy of continuity: Introduce changes and developments in continuity with established examples and approaches. - Maintain the existing examples for default setting and the 'mad' override. - Establish regression test based on the default setting and 'mad' override to ensure that a user of the deployment method can continue to do the same thing they used to do. - Maintain and extend the use of overridable variable definitions for the attributes of a lab. - Maintain and extend the use of command line parameters for configuration selection, such as "-c 'simplex'". - Maintain and extend the existing workflow: "exporting variables, setup_network.sh, setup_configation.sh, destroy_configuration.sh, destroy_network.sh". A) Maintain configurations for more than one virtual cluster: Motivation: allow a lab's attributes to be recalled from a configuration file and operate upon that lab specifically. Establish a precedent for a configuration file used to override the default attributes. Refer to the README.rst "Overview" section which lists environment variables CONTROLLER, WORKER, BRIDGE_INTERFACE, EXTERNAL_NETWORK, EXTERNAL_IP. Provide a default configuration file that will reset the variables to defaults as they currently exist within the deployment/libvirt scripts, including: BRIDGE_INTERFACE=${BRIDGE_INTERFACE:-stxbr} EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} CONFIGURATION=${CONFIGURATION:-simplex} CONTROLLER=${CONTROLLER:-controller} WORKER=${WORKER:-worker} STORAGE=${STORAGE:-storage} WORKER_NODES_NUMBER=${WORKER_NODES_NUMBER:-1} STORAGE_NODES_NUMBER=${STORAGE_NODES_NUMBER:-1} Provide an example configuration file that sets a lab's attributes deviating from the default. Especially, the default and the example should co-exist. Consider honouring the "mad" example in README.rst. If necessary provide an option to select values, or a script to set variables, from that configuration file. B) Improve usage and selection of host's resources: Motivation: allow lab specific attributes for the host's resources and provide tools to inspect those resources within the contexts of the virtual labs and/or overall Note: Ensure that all changes are providing defaults that are equivalent to the existing implementation. Values to add to the lab's attributes: Add DOMAIN_DIRECTORY to the set of overridable variables Add an override variable for the DISK file location for each node in a virtual lab. (currently hardcoded /var/lib/libvirt/images in functions.sh) Add an override variable for the MEMORY setting for each node (currently XML hardcoded ) Add an override variable for the CPU setting of each node (currently XML hardcoded ) Add scripting to assist with supervising the host's resources, such as: - listing the lab's nodes and networks; - inspecting the lab's network configurations; - inspecting the host's and lab's disk usage per configured disk; - listing a lab's nodes' cpu and memory allocations C) Isolate cluster networks where more than one cluster may be running: Motivation: on a host that has a capacity to run virtual clusters, ensure that there is no networking crosstalk between the running clusters. Provide scripting to add/remove iptables restrictions for a lab's networks. Initially assume no inter-cluster communication, and only the OAM network will route to external networks. Include: - ipv4 and/or ipv6 - a lab specific iptables CHAIN Probably: omit running this script automatically, since it changes the deployment behaviour. Consider adding an optional parameter to setup_network.sh. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Mon Jul 10 12:35:06 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 10 Jul 2023 12:35:06 +0000 Subject: [Starlingx-discuss] proposal to add Jim Gauld for core reviewer in the "config" repo In-Reply-To: References: Message-ID: +1 -----Original Message----- From: Chris Friesen Sent: Thursday, June 29, 2023 11:22 AM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] proposal to add Jim Gauld for core reviewer in the "config" repo Jim Gauld has been around for a long time and has a deep historical knowledge of the StarlingX project.? He has been dealing with quite a few issues in the config repo, mostly related to Kubernetes issues and upgrades and has an excellent understanding of how the pieces fit together. As such, I'd like to propose Jim as an addition to the core reviewer list for the config repo. Thanks, Chris _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io From Greg.Waines at windriver.com Mon Jul 10 12:42:37 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 10 Jul 2023 12:42:37 +0000 Subject: [Starlingx-discuss] How to get standby controller as active after active controller down In-Reply-To: References: Message-ID: The standby controller should automatically ?become active? on detecting that the previously active controller is failed. Greg. From: open infra Sent: Wednesday, July 5, 2023 6:02 AM To: StarlingX ML Subject: [Starlingx-discuss] How to get standby controller as active after active controller down CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, In a stx standard dedicated storage setup, active controller was down (disk failure). Now I need to get the stand by controller as the active controller (in order to get the failed controller up and running). swatc is required to run in an active controller. So, how to make stand by as the active controller itself? Regards, Danishka -------------- next part -------------- An HTML attachment was scrubbed... URL: From ThalesElero.Cervi at windriver.com Mon Jul 10 13:19:34 2023 From: ThalesElero.Cervi at windriver.com (Cervi, Thales Elero) Date: Mon, 10 Jul 2023 13:19:34 +0000 Subject: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo Message-ID: Luan has been actively contributing to the stx-openstack application and is very active not only on submitting his changes, but also on reviewing code submitted by other colleagues. He fixed several bugs and worked on the migration of OpenStack images to be based on stx-debian and on the OpenStack clients containerization (an ongoing work that will be much helpful towards Antelope update). He has currently an excellent understanding on how the app works and is built. So, I'd like to propose Luan as an addition to the core reviewer list for the config openstack-armada-app. Thales Elero Cervi -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Mon Jul 10 13:21:04 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 10 Jul 2023 13:21:04 +0000 Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization In-Reply-To: References: Message-ID: Where is the 'libvirt virtual deployment method' documented under docs.starlingx.io ? Is it here ? https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_environ.html ( and corresponding spots for other configs ) So you're saying your changes won't impact the current documentation of the 'libvirt virtual deployment method' ? Greg. From: Thebeau, Michel Sent: Monday, July 10, 2023 8:55 AM To: Waines, Greg ; starlingx-discuss at lists.starlingx.io Cc: Balaraj, Juanita ; Stone, Ronald Subject: Re: Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Good morning Greg, Thanks for letting me know. I was not aware that the documents were out-of-sync and that the examples under virtual deployment were out-of-date. Especially: I had not noticed any out-of-date instruction while using the examples from virtual section. To answer your first question: I have an intention of not impacting the canonical examples and current usage/use-case. In this way I did not anticipate documentation changes. I especially intend that if one were using the libvirt deployment method as it is presented today, then the changes I intend would have no impact on that usage. I am not prepared to accept the assignment this morning. I can, for example, contribute to ensuring that a merging of the documents will continue to accurately reflect the libvirt virtual deployment method - either by proposing changes or reviewing the changes. Please feel free to bring me into the conversation. M ________________________________ From: Waines, Greg > Sent: 10 July 2023 8:24 AM To: Thebeau, Michel >; starlingx-discuss at lists.starlingx.io > Cc: Balaraj, Juanita >; Stone, Ronald > Subject: RE: Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Hey Mich, Thanksfor looking at this. Do you intent to update the virtual install guides as well ? ... as part of this work ? e.g. https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_install_kubernetes.html A heads up if you do ... (I think I've mentioned this a couple of times) * The bare-metal install guides have been enhanced/updated and maintained over the last few stx releases * ... but the virtual install guides have not * E.g. if you compare * https://docs.starlingx.io/deploy_install_guides/release/bare_metal/aio_simplex_install_kubernetes.html * And * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex.html * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_environ.html * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_install_kubernetes.html you'll see several differences that are not necessarily due virtual versus bare-metal. * We (doc team) did not maintain the virtual install guides because we were thinking that * It was too much overhead maintaining both guides, * Instead we were going to combine the guides * And just have in the very few places, the difference between virtual versus bare-metal * BUT ... we have not had time to look at this. * * If you are interested in doing this ... let me, Juanita and Ron know and we can provide some guidance here. Greg. From: Thebeau, Michel > Sent: Wednesday, June 28, 2023 3:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Hi, I prepared the following description of enhancements I intend towards the libvirt virtual deployment method. Please let me know I should follow a particular procedure. Otherwise I intend to create a story in storyboard. Mitch. === Starlingx Libvirt deployment method host utilization enhancements References: "Install StarlingX Kubernetes in a virtual environment" - https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html#index-install-r7-8966076f0e81 Libvirt deployment method in starlingx/tools - https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt Libvirt deployment method moved this week to starlingx/virtual-deployment - https://opendev.org/starlingx/virtual-deployment/src/branch/master/libvirt Motivation is to: A) maintain attributes for more than one virtual lab B) improve the usage and selection of the host's resources for disk, memory and cpu C) isolate cluster networks where more than one virtual lab may be running Philosophy of continuity: Introduce changes and developments in continuity with established examples and approaches. - Maintain the existing examples for default setting and the 'mad' override. - Establish regression test based on the default setting and 'mad' override to ensure that a user of the deployment method can continue to do the same thing they used to do. - Maintain and extend the use of overridable variable definitions for the attributes of a lab. - Maintain and extend the use of command line parameters for configuration selection, such as "-c 'simplex'". - Maintain and extend the existing workflow: "exporting variables, setup_network.sh, setup_configation.sh, destroy_configuration.sh, destroy_network.sh". A) Maintain configurations for more than one virtual cluster: Motivation: allow a lab's attributes to be recalled from a configuration file and operate upon that lab specifically. Establish a precedent for a configuration file used to override the default attributes. Refer to the README.rst "Overview" section which lists environment variables CONTROLLER, WORKER, BRIDGE_INTERFACE, EXTERNAL_NETWORK, EXTERNAL_IP. Provide a default configuration file that will reset the variables to defaults as they currently exist within the deployment/libvirt scripts, including: BRIDGE_INTERFACE=${BRIDGE_INTERFACE:-stxbr} EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} CONFIGURATION=${CONFIGURATION:-simplex} CONTROLLER=${CONTROLLER:-controller} WORKER=${WORKER:-worker} STORAGE=${STORAGE:-storage} WORKER_NODES_NUMBER=${WORKER_NODES_NUMBER:-1} STORAGE_NODES_NUMBER=${STORAGE_NODES_NUMBER:-1} Provide an example configuration file that sets a lab's attributes deviating from the default. Especially, the default and the example should co-exist. Consider honouring the "mad" example in README.rst. If necessary provide an option to select values, or a script to set variables, from that configuration file. B) Improve usage and selection of host's resources: Motivation: allow lab specific attributes for the host's resources and provide tools to inspect those resources within the contexts of the virtual labs and/or overall Note: Ensure that all changes are providing defaults that are equivalent to the existing implementation. Values to add to the lab's attributes: Add DOMAIN_DIRECTORY to the set of overridable variables Add an override variable for the DISK file location for each node in a virtual lab. (currently hardcoded /var/lib/libvirt/images in functions.sh) Add an override variable for the MEMORY setting for each node (currently XML hardcoded ) Add an override variable for the CPU setting of each node (currently XML hardcoded ) Add scripting to assist with supervising the host's resources, such as: - listing the lab's nodes and networks; - inspecting the lab's network configurations; - inspecting the host's and lab's disk usage per configured disk; - listing a lab's nodes' cpu and memory allocations C) Isolate cluster networks where more than one cluster may be running: Motivation: on a host that has a capacity to run virtual clusters, ensure that there is no networking crosstalk between the running clusters. Provide scripting to add/remove iptables restrictions for a lab's networks. Initially assume no inter-cluster communication, and only the OAM network will route to external networks. Include: - ipv4 and/or ipv6 - a lab specific iptables CHAIN Probably: omit running this script automatically, since it changes the deployment behaviour. Consider adding an optional parameter to setup_network.sh. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Mon Jul 10 13:24:58 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Mon, 10 Jul 2023 13:24:58 +0000 Subject: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo In-Reply-To: References: Message-ID: +1 From: Cervi, Thales Elero Sent: Monday, July 10, 2023 9:20 AM To: StarlingX ML Subject: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo Luan has been actively contributing to the stx-openstack application and is very active not only on submitting his changes, but also on reviewing code submitted by other colleagues. He fixed several bugs and worked on the migration of OpenStack images to be based on stx-debian and on the OpenStack clients containerization (an ongoing work that will be much helpful towards Antelope update). He has currently an excellent understanding on how the app works and is built. So, I'd like to propose Luan as an addition to the core reviewer list for the config openstack-armada-app. Thales Elero Cervi -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lucas.DeAtaidesBarreto at windriver.com Mon Jul 10 13:35:07 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Mon, 10 Jul 2023 13:35:07 +0000 Subject: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo In-Reply-To: References: Message-ID: +1 ________________________________ From: Waines, Greg Sent: Monday, July 10, 2023 10:24 AM To: Cervi, Thales Elero ; StarlingX ML Subject: Re: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo +1 From: Cervi, Thales Elero Sent: Monday, July 10, 2023 9:20 AM To: StarlingX ML Subject: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo Luan has been actively contributing to the stx-openstack application and is very active not only on submitting his changes, but also on reviewing code submitted by other colleagues. He fixed several bugs and worked on the migration of OpenStack images to be based on stx-debian and on the OpenStack clients containerization (an ongoing work that will be much helpful towards Antelope update). He has currently an excellent understanding on how the app works and is built. So, I'd like to propose Luan as an addition to the core reviewer list for the config openstack-armada-app. Thales Elero Cervi -------------- next part -------------- An HTML attachment was scrubbed... URL: From Michel.Thebeau at windriver.com Mon Jul 10 12:08:09 2023 From: Michel.Thebeau at windriver.com (Thebeau, Michel) Date: Mon, 10 Jul 2023 12:08:09 +0000 Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization In-Reply-To: References: Message-ID: Good morning Bruno, Thank you. I am aware of the VirtualBox deployment method and the work of your team members. "Basically, for now, we don't remove all the detailed procedures" The installation guides of Starlingx present a "lesson" in the use of Starlingx for those who are exploring the project. Please consider keeping and maintaining these guides as "canonical" examples of deploying Starlingx. Our libvirt and VirtualBox deployment methods are intended to make Starlingx more accessible to those who are learning about the project: not requiring them to have dedicated hardware to explore Starlingx. In this sense, you may consider my intentions towards the libvirt deployment method to include this intention: to have no impact on the canonical examples. M ________________________________ From: Bruno Drugowick Muniz Sent: 04 July 2023 3:17 PM To: Thebeau, Michel ; starlingx-discuss at lists.starlingx.io Subject: Re: Intentions toward enhancements for Starlingx Libvirt deployment method host utilization CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hello, Mitch. * "Please let me know I should follow a particular procedure. Otherwise I intend to create a story in storyboard." I believe that's the way to go. Just so you know, for the work under the /virtualbox directory of the same repository, we used the original story with the Task that merged the code back in 2019, adding new Tasks to it. Regarding the "Install StarlingX Kubernetes in a virtual environment" page, you might want to look at what we're proposing at https://review.opendev.org/c/starlingx/docs/+/886178. Basically, for now, we don't remove all the detailed procedures but provide an additional "automated install" guide at the top. Regards, Bruno. ________________________________ From: Thebeau, Michel Sent: Wednesday, June 28, 2023 16:50 To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization You don't often get email from michel.thebeau 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. Hi, I prepared the following description of enhancements I intend towards the libvirt virtual deployment method. Please let me know I should follow a particular procedure. Otherwise I intend to create a story in storyboard. Mitch. === Starlingx Libvirt deployment method host utilization enhancements References: "Install StarlingX Kubernetes in a virtual environment" - https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html#index-install-r7-8966076f0e81 Libvirt deployment method in starlingx/tools - https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt Libvirt deployment method moved this week to starlingx/virtual-deployment - https://opendev.org/starlingx/virtual-deployment/src/branch/master/libvirt Motivation is to: A) maintain attributes for more than one virtual lab B) improve the usage and selection of the host's resources for disk, memory and cpu C) isolate cluster networks where more than one virtual lab may be running Philosophy of continuity: Introduce changes and developments in continuity with established examples and approaches. - Maintain the existing examples for default setting and the 'mad' override. - Establish regression test based on the default setting and 'mad' override to ensure that a user of the deployment method can continue to do the same thing they used to do. - Maintain and extend the use of overridable variable definitions for the attributes of a lab. - Maintain and extend the use of command line parameters for configuration selection, such as "-c 'simplex'". - Maintain and extend the existing workflow: "exporting variables, setup_network.sh, setup_configation.sh, destroy_configuration.sh, destroy_network.sh". A) Maintain configurations for more than one virtual cluster: Motivation: allow a lab's attributes to be recalled from a configuration file and operate upon that lab specifically. Establish a precedent for a configuration file used to override the default attributes. Refer to the README.rst "Overview" section which lists environment variables CONTROLLER, WORKER, BRIDGE_INTERFACE, EXTERNAL_NETWORK, EXTERNAL_IP. Provide a default configuration file that will reset the variables to defaults as they currently exist within the deployment/libvirt scripts, including: BRIDGE_INTERFACE=${BRIDGE_INTERFACE:-stxbr} EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} CONFIGURATION=${CONFIGURATION:-simplex} CONTROLLER=${CONTROLLER:-controller} WORKER=${WORKER:-worker} STORAGE=${STORAGE:-storage} WORKER_NODES_NUMBER=${WORKER_NODES_NUMBER:-1} STORAGE_NODES_NUMBER=${STORAGE_NODES_NUMBER:-1} Provide an example configuration file that sets a lab's attributes deviating from the default. Especially, the default and the example should co-exist. Consider honouring the "mad" example in README.rst. If necessary provide an option to select values, or a script to set variables, from that configuration file. B) Improve usage and selection of host's resources: Motivation: allow lab specific attributes for the host's resources and provide tools to inspect those resources within the contexts of the virtual labs and/or overall Note: Ensure that all changes are providing defaults that are equivalent to the existing implementation. Values to add to the lab's attributes: Add DOMAIN_DIRECTORY to the set of overridable variables Add an override variable for the DISK file location for each node in a virtual lab. (currently hardcoded /var/lib/libvirt/images in functions.sh) Add an override variable for the MEMORY setting for each node (currently XML hardcoded ) Add an override variable for the CPU setting of each node (currently XML hardcoded ) Add scripting to assist with supervising the host's resources, such as: - listing the lab's nodes and networks; - inspecting the lab's network configurations; - inspecting the host's and lab's disk usage per configured disk; - listing a lab's nodes' cpu and memory allocations C) Isolate cluster networks where more than one cluster may be running: Motivation: on a host that has a capacity to run virtual clusters, ensure that there is no networking crosstalk between the running clusters. Provide scripting to add/remove iptables restrictions for a lab's networks. Initially assume no inter-cluster communication, and only the OAM network will route to external networks. Include: - ipv4 and/or ipv6 - a lab specific iptables CHAIN Probably: omit running this script automatically, since it changes the deployment behaviour. Consider adding an optional parameter to setup_network.sh. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Michel.Thebeau at windriver.com Mon Jul 10 12:54:59 2023 From: Michel.Thebeau at windriver.com (Thebeau, Michel) Date: Mon, 10 Jul 2023 12:54:59 +0000 Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization In-Reply-To: References: Message-ID: Good morning Greg, Thanks for letting me know. I was not aware that the documents were out-of-sync and that the examples under virtual deployment were out-of-date. Especially: I had not noticed any out-of-date instruction while using the examples from virtual section. To answer your first question: I have an intention of not impacting the canonical examples and current usage/use-case. In this way I did not anticipate documentation changes. I especially intend that if one were using the libvirt deployment method as it is presented today, then the changes I intend would have no impact on that usage. I am not prepared to accept the assignment this morning. I can, for example, contribute to ensuring that a merging of the documents will continue to accurately reflect the libvirt virtual deployment method - either by proposing changes or reviewing the changes. Please feel free to bring me into the conversation. M ________________________________ From: Waines, Greg Sent: 10 July 2023 8:24 AM To: Thebeau, Michel ; starlingx-discuss at lists.starlingx.io Cc: Balaraj, Juanita ; Stone, Ronald Subject: RE: Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Hey Mich, Thanksfor looking at this. Do you intent to update the virtual install guides as well ? ? as part of this work ? e.g. https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_install_kubernetes.html A heads up if you do ? (I think I?ve mentioned this a couple of times) * The bare-metal install guides have been enhanced/updated and maintained over the last few stx releases * ? but the virtual install guides have not * E.g. if you compare * https://docs.starlingx.io/deploy_install_guides/release/bare_metal/aio_simplex_install_kubernetes.html * And * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex.html * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_environ.html * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_install_kubernetes.html you?ll see several differences that are not necessarily due virtual versus bare-metal. * We (doc team) did not maintain the virtual install guides because we were thinking that * It was too much overhead maintaining both guides, * Instead we were going to combine the guides * And just have in the very few places, the difference between virtual versus bare-metal * BUT ? we have not had time to look at this. * * If you are interested in doing this ? let me, Juanita and Ron know and we can provide some guidance here. Greg. From: Thebeau, Michel Sent: Wednesday, June 28, 2023 3:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Hi, I prepared the following description of enhancements I intend towards the libvirt virtual deployment method. Please let me know I should follow a particular procedure. Otherwise I intend to create a story in storyboard. Mitch. === Starlingx Libvirt deployment method host utilization enhancements References: "Install StarlingX Kubernetes in a virtual environment" - https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html#index-install-r7-8966076f0e81 Libvirt deployment method in starlingx/tools - https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt Libvirt deployment method moved this week to starlingx/virtual-deployment - https://opendev.org/starlingx/virtual-deployment/src/branch/master/libvirt Motivation is to: A) maintain attributes for more than one virtual lab B) improve the usage and selection of the host's resources for disk, memory and cpu C) isolate cluster networks where more than one virtual lab may be running Philosophy of continuity: Introduce changes and developments in continuity with established examples and approaches. - Maintain the existing examples for default setting and the 'mad' override. - Establish regression test based on the default setting and 'mad' override to ensure that a user of the deployment method can continue to do the same thing they used to do. - Maintain and extend the use of overridable variable definitions for the attributes of a lab. - Maintain and extend the use of command line parameters for configuration selection, such as "-c 'simplex'". - Maintain and extend the existing workflow: "exporting variables, setup_network.sh, setup_configation.sh, destroy_configuration.sh, destroy_network.sh". A) Maintain configurations for more than one virtual cluster: Motivation: allow a lab's attributes to be recalled from a configuration file and operate upon that lab specifically. Establish a precedent for a configuration file used to override the default attributes. Refer to the README.rst "Overview" section which lists environment variables CONTROLLER, WORKER, BRIDGE_INTERFACE, EXTERNAL_NETWORK, EXTERNAL_IP. Provide a default configuration file that will reset the variables to defaults as they currently exist within the deployment/libvirt scripts, including: BRIDGE_INTERFACE=${BRIDGE_INTERFACE:-stxbr} EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} CONFIGURATION=${CONFIGURATION:-simplex} CONTROLLER=${CONTROLLER:-controller} WORKER=${WORKER:-worker} STORAGE=${STORAGE:-storage} WORKER_NODES_NUMBER=${WORKER_NODES_NUMBER:-1} STORAGE_NODES_NUMBER=${STORAGE_NODES_NUMBER:-1} Provide an example configuration file that sets a lab's attributes deviating from the default. Especially, the default and the example should co-exist. Consider honouring the "mad" example in README.rst. If necessary provide an option to select values, or a script to set variables, from that configuration file. B) Improve usage and selection of host's resources: Motivation: allow lab specific attributes for the host's resources and provide tools to inspect those resources within the contexts of the virtual labs and/or overall Note: Ensure that all changes are providing defaults that are equivalent to the existing implementation. Values to add to the lab's attributes: Add DOMAIN_DIRECTORY to the set of overridable variables Add an override variable for the DISK file location for each node in a virtual lab. (currently hardcoded /var/lib/libvirt/images in functions.sh) Add an override variable for the MEMORY setting for each node (currently XML hardcoded ) Add an override variable for the CPU setting of each node (currently XML hardcoded ) Add scripting to assist with supervising the host's resources, such as: - listing the lab's nodes and networks; - inspecting the lab's network configurations; - inspecting the host's and lab's disk usage per configured disk; - listing a lab's nodes' cpu and memory allocations C) Isolate cluster networks where more than one cluster may be running: Motivation: on a host that has a capacity to run virtual clusters, ensure that there is no networking crosstalk between the running clusters. Provide scripting to add/remove iptables restrictions for a lab's networks. Initially assume no inter-cluster communication, and only the OAM network will route to external networks. Include: - ipv4 and/or ipv6 - a lab specific iptables CHAIN Probably: omit running this script automatically, since it changes the deployment behaviour. Consider adding an optional parameter to setup_network.sh. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Michel.Thebeau at windriver.com Mon Jul 10 13:48:19 2023 From: Michel.Thebeau at windriver.com (Thebeau, Michel) Date: Mon, 10 Jul 2023 13:48:19 +0000 Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization In-Reply-To: References: Message-ID: Hi Greg, Yes, that's the example for aio-simplex specifically. I would have referred to the parent page which links to each deployment option: https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html Each of the listed deployment options under "Install StarlingX Kubernetes in a virtual environment" has the instruction for libvirt method. Yes, I am saying that I am intending that the changes should not impact anything that a user would do currently. I want to add options to better use a host's resources for disk, memory and CPU without affecting the current examples and default behaviour presented in the Starlingx documentation (and the libvirt method's README) M ________________________________ From: Waines, Greg Sent: 10 July 2023 9:21 AM To: Thebeau, Michel ; starlingx-discuss at lists.starlingx.io Cc: Balaraj, Juanita ; Stone, Ronald Subject: RE: Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Where is the ?libvirt virtual deployment method? documented under docs.starlingx.io ? Is it here ? https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_environ.html ( and corresponding spots for other configs ) So you?re saying your changes won?t impact the current documentation of the ?libvirt virtual deployment method? ? Greg. From: Thebeau, Michel Sent: Monday, July 10, 2023 8:55 AM To: Waines, Greg ; starlingx-discuss at lists.starlingx.io Cc: Balaraj, Juanita ; Stone, Ronald Subject: Re: Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Good morning Greg, Thanks for letting me know. I was not aware that the documents were out-of-sync and that the examples under virtual deployment were out-of-date. Especially: I had not noticed any out-of-date instruction while using the examples from virtual section. To answer your first question: I have an intention of not impacting the canonical examples and current usage/use-case. In this way I did not anticipate documentation changes. I especially intend that if one were using the libvirt deployment method as it is presented today, then the changes I intend would have no impact on that usage. I am not prepared to accept the assignment this morning. I can, for example, contribute to ensuring that a merging of the documents will continue to accurately reflect the libvirt virtual deployment method - either by proposing changes or reviewing the changes. Please feel free to bring me into the conversation. M ________________________________ From: Waines, Greg > Sent: 10 July 2023 8:24 AM To: Thebeau, Michel >; starlingx-discuss at lists.starlingx.io > Cc: Balaraj, Juanita >; Stone, Ronald > Subject: RE: Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Hey Mich, Thanksfor looking at this. Do you intent to update the virtual install guides as well ? ? as part of this work ? e.g. https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_install_kubernetes.html A heads up if you do ? (I think I?ve mentioned this a couple of times) * The bare-metal install guides have been enhanced/updated and maintained over the last few stx releases * ? but the virtual install guides have not * E.g. if you compare * https://docs.starlingx.io/deploy_install_guides/release/bare_metal/aio_simplex_install_kubernetes.html * And * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex.html * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_environ.html * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_install_kubernetes.html you?ll see several differences that are not necessarily due virtual versus bare-metal. * We (doc team) did not maintain the virtual install guides because we were thinking that * It was too much overhead maintaining both guides, * Instead we were going to combine the guides * And just have in the very few places, the difference between virtual versus bare-metal * BUT ? we have not had time to look at this. * * If you are interested in doing this ? let me, Juanita and Ron know and we can provide some guidance here. Greg. From: Thebeau, Michel > Sent: Wednesday, June 28, 2023 3:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Hi, I prepared the following description of enhancements I intend towards the libvirt virtual deployment method. Please let me know I should follow a particular procedure. Otherwise I intend to create a story in storyboard. Mitch. === Starlingx Libvirt deployment method host utilization enhancements References: "Install StarlingX Kubernetes in a virtual environment" - https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html#index-install-r7-8966076f0e81 Libvirt deployment method in starlingx/tools - https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt Libvirt deployment method moved this week to starlingx/virtual-deployment - https://opendev.org/starlingx/virtual-deployment/src/branch/master/libvirt Motivation is to: A) maintain attributes for more than one virtual lab B) improve the usage and selection of the host's resources for disk, memory and cpu C) isolate cluster networks where more than one virtual lab may be running Philosophy of continuity: Introduce changes and developments in continuity with established examples and approaches. - Maintain the existing examples for default setting and the 'mad' override. - Establish regression test based on the default setting and 'mad' override to ensure that a user of the deployment method can continue to do the same thing they used to do. - Maintain and extend the use of overridable variable definitions for the attributes of a lab. - Maintain and extend the use of command line parameters for configuration selection, such as "-c 'simplex'". - Maintain and extend the existing workflow: "exporting variables, setup_network.sh, setup_configation.sh, destroy_configuration.sh, destroy_network.sh". A) Maintain configurations for more than one virtual cluster: Motivation: allow a lab's attributes to be recalled from a configuration file and operate upon that lab specifically. Establish a precedent for a configuration file used to override the default attributes. Refer to the README.rst "Overview" section which lists environment variables CONTROLLER, WORKER, BRIDGE_INTERFACE, EXTERNAL_NETWORK, EXTERNAL_IP. Provide a default configuration file that will reset the variables to defaults as they currently exist within the deployment/libvirt scripts, including: BRIDGE_INTERFACE=${BRIDGE_INTERFACE:-stxbr} EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} CONFIGURATION=${CONFIGURATION:-simplex} CONTROLLER=${CONTROLLER:-controller} WORKER=${WORKER:-worker} STORAGE=${STORAGE:-storage} WORKER_NODES_NUMBER=${WORKER_NODES_NUMBER:-1} STORAGE_NODES_NUMBER=${STORAGE_NODES_NUMBER:-1} Provide an example configuration file that sets a lab's attributes deviating from the default. Especially, the default and the example should co-exist. Consider honouring the "mad" example in README.rst. If necessary provide an option to select values, or a script to set variables, from that configuration file. B) Improve usage and selection of host's resources: Motivation: allow lab specific attributes for the host's resources and provide tools to inspect those resources within the contexts of the virtual labs and/or overall Note: Ensure that all changes are providing defaults that are equivalent to the existing implementation. Values to add to the lab's attributes: Add DOMAIN_DIRECTORY to the set of overridable variables Add an override variable for the DISK file location for each node in a virtual lab. (currently hardcoded /var/lib/libvirt/images in functions.sh) Add an override variable for the MEMORY setting for each node (currently XML hardcoded ) Add an override variable for the CPU setting of each node (currently XML hardcoded ) Add scripting to assist with supervising the host's resources, such as: - listing the lab's nodes and networks; - inspecting the lab's network configurations; - inspecting the host's and lab's disk usage per configured disk; - listing a lab's nodes' cpu and memory allocations C) Isolate cluster networks where more than one cluster may be running: Motivation: on a host that has a capacity to run virtual clusters, ensure that there is no networking crosstalk between the running clusters. Provide scripting to add/remove iptables restrictions for a lab's networks. Initially assume no inter-cluster communication, and only the OAM network will route to external networks. Include: - ipv4 and/or ipv6 - a lab specific iptables CHAIN Probably: omit running this script automatically, since it changes the deployment behaviour. Consider adding an optional parameter to setup_network.sh. -------------- next part -------------- An HTML attachment was scrubbed... URL: From douglas.pereira at encora.com Mon Jul 10 14:05:36 2023 From: douglas.pereira at encora.com (Douglas Lopes Pereira) Date: Mon, 10 Jul 2023 14:05:36 +0000 Subject: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo In-Reply-To: References: Message-ID: +1 Douglas Lopes Pereira Software Development Manager M: +55 (19) 99212-3212 Campinas, BR [Encora] [We are proud to be recognized as Leaders in digital engineering services by Zinnov zones] ________________________________ From: De Ataides Barreto, Lucas Sent: Monday, July 10, 2023 10:35 AM To: Waines, Greg ; Cervi, Thales Elero ; StarlingX ML Subject: Re: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo You don't often get email from lucas.deataidesbarreto 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. +1 ________________________________ From: Waines, Greg Sent: Monday, July 10, 2023 10:24 AM To: Cervi, Thales Elero ; StarlingX ML Subject: Re: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo +1 From: Cervi, Thales Elero Sent: Monday, July 10, 2023 9:20 AM To: StarlingX ML Subject: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo Luan has been actively contributing to the stx-openstack application and is very active not only on submitting his changes, but also on reviewing code submitted by other colleagues. He fixed several bugs and worked on the migration of OpenStack images to be based on stx-debian and on the OpenStack clients containerization (an ongoing work that will be much helpful towards Antelope update). He has currently an excellent understanding on how the app works and is built. So, I'd like to propose Luan as an addition to the core reviewer list for the config openstack-armada-app. Thales Elero Cervi -------------- next part -------------- An HTML attachment was scrubbed... URL: From Robert.Church at windriver.com Mon Jul 10 17:11:20 2023 From: Robert.Church at windriver.com (Church, Robert) Date: Mon, 10 Jul 2023 17:11:20 +0000 Subject: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo In-Reply-To: References: Message-ID: +1 From: Douglas Lopes Pereira Date: Monday, July 10, 2023 at 9:08 AM To: De Ataides Barreto, Lucas , Waines, Greg , Cervi, Thales Elero , StarlingX ML Subject: Re: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. +1 Douglas Lopes Pereira Software Development Manager M: +55 (19) 99212-3212 Campinas, BR [Image removed by sender. Encora] [Image removed by sender. We are proud to be recognized as Leaders in digital engineering services by Zinnov zones] ________________________________ From: De Ataides Barreto, Lucas Sent: Monday, July 10, 2023 10:35 AM To: Waines, Greg ; Cervi, Thales Elero ; StarlingX ML Subject: Re: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo You don't often get email from lucas.deataidesbarreto 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. +1 ________________________________ From: Waines, Greg Sent: Monday, July 10, 2023 10:24 AM To: Cervi, Thales Elero ; StarlingX ML Subject: Re: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo +1 From: Cervi, Thales Elero Sent: Monday, July 10, 2023 9:20 AM To: StarlingX ML Subject: [Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo Luan has been actively contributing to the stx-openstack application and is very active not only on submitting his changes, but also on reviewing code submitted by other colleagues. He fixed several bugs and worked on the migration of OpenStack images to be based on stx-debian and on the OpenStack clients containerization (an ongoing work that will be much helpful towards Antelope update). He has currently an excellent understanding on how the app works and is built. So, I'd like to propose Luan as an addition to the core reviewer list for the config openstack-armada-app. Thales Elero Cervi -------------- next part -------------- An HTML attachment was scrubbed... URL: From Linda.Wang at windriver.com Mon Jul 10 21:11:48 2023 From: Linda.Wang at windriver.com (Wang, Linda) Date: Mon, 10 Jul 2023 21:11:48 +0000 Subject: [Starlingx-discuss] Bi-Weekly StartlingX OS Distro & Multi-OS Meeting: May 31, 2023 Message-ID: May 31, 2023 Attendees: Davlet, Mark, Charles, Jackie Huang, Scott, Xuan, Trevor Tao 1. General Topics * 1.1 Split package list between repositories (ISO and container images) * Separation of the list is done per Davlet. * AI: Devlet will check the documentation on package list. * 1.2 Log into the git before download the source. * * How to pass the credential through the tooling layer when log into git repo. * * workaround: currently use repo sync outside of the containers. * * AI: Scott to write up a feature request for the tool - file a request in Story Board. * Created: https://storyboard.openstack.org/#!/story/2010777 * 1.3 Pre-patch ISO (Luis) (Carols replacing Luis Barbosa) * AI: to invite Carlos Pocahy to this meeting to discuss Pre-patch ISO. (lwang8: Ping Carlos and his manager to make sure he attends) 2. ARM Support * Send email to the mailing list on * How to review the packages list for CENGN build * CENGN: move to another provider. Early development don't expect anything for at least 2 months. * Wind River willl be provide it. Will be available via Wind River Lab. * Ampere would liketo provide 6 servers * They like to know where the new location is, so that they can send the servers to the new location? * AI#1: Scott will talk to his manager to see where the new location is, to share with Jackie and ARM. * We do NOT have rack space or power for the proposed equipment at this time. * Porting still in progress * Work with ARM company and help them and setup it up in their lab. * all packages built, started with StartlingX 8.0 master for ARM. * RT kernel still failed to build * for ARM Build, we also need to re-generate container image for ARM arch. For container images, we push them to docker hub, and StartlingX. * AI#2: Sent email to StartlingX mailing list to get temporay access to his own docker hub. [Done] * push to staging area first to gain confidence. * Packages for x86_64 are in CNGN, need to push ARM packages there.. how to do so? * ELF SDK is used to build image. Need to push the SDK to CNGN. * Need to change meta-lat layer for ELF SDK, but want to link the task to different repo, but can't. * meta-lat layer is not in the StartlingX repo, but its in github repo. fork it.. do a pull request to github lab for any changes. * How to moderate source code, add the machine-type = aarch 64/arm, add another name for UIO for ARM. * AI#3 Jackie need to discuss how to use these naming mechanism. * AI#4 also the branching name. How to build ARM branch in addition to X86_64. * 'Build server stats' email, Scott replied to the email on the mailing list: * Build server recommendation: At least 4 disks, and 12 T storage space, 128 G memory. possible ram disk for builds * AI#5 Test server config: Scott will check with QA team to provide needed info. * 3.0 StartlingX 8.0 * ISO size bigger than 4G * Resolved with option parameters passing into ISO build. * AI#6: Need to look at the existing scripts to implement this functionality * 3.1 SPEC to be written by Mark regarding new direction for the kernel, possibly to use the newer version of Debian kernel * Proposal is to have kernel to track Debian version. * 3.2 SPEC from Chuck on OSTree generation on the controller, pending review. June 14, 2023 Attendees: Davlet, Mark, Charles. Linda, Juanita Open Infrastructure Conference week. No quorum June 28, 2023 Attendees: Davlet, Mark, Linda, Charles Due to lack of attendees, No quorum today. Next Meeting: July 12, 2023 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Mon Jul 10 23:24:07 2023 From: kennelson11 at gmail.com (Kendall Nelson) Date: Mon, 10 Jul 2023 18:24:07 -0500 Subject: [Starlingx-discuss] Fwd: vPTG October 2023 Dates & Registration Kickoff In-Reply-To: References: Message-ID: Hello Everyone! The next PTG[1] will take place October 23-27, 2023 virtually! Registration is now open[2] and free for all to attend. Keep an eye out in the coming weeks because I will send along the team sign up to collect groups interested in participating. Thanks! -Kendall Nelson(diablo_rojo) [1] https://openinfra.dev/ptg/ [2] http://ptg2023.openinfra.dev/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ramaswamy.Subramanian at windriver.com Tue Jul 11 13:51:14 2023 From: Ramaswamy.Subramanian at windriver.com (Subramanian, Ramaswamy) Date: Tue, 11 Jul 2023 13:51:14 +0000 Subject: [Starlingx-discuss] DistCloud/Flock Services Project Meeting Minutes Message-ID: July 11, 2023: * Github and StarlingX repository synchronization is restored. * StarlingX 9.0 Release: * Feature development in progress. More details available in the release planning spread sheet. * Bug cleanup (more than 1 year old with no activity) * Closed. ( https://bugs.launchpad.net/starlingx/+bug/1869249 https://bugs.launchpad.net/starlingx/+bug/1875553 ) * Candidate for Closure. https://bugs.launchpad.net/starlingx/+bug/1858937 https://bugs.launchpad.net/starlingx/+bug/1852734 https://bugs.launchpad.net/starlingx/+bug/1852729 https://bugs.launchpad.net/starlingx/+bug/1852836 https://bugs.launchpad.net/starlingx/+bug/1860473 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Tue Jul 11 13:10:39 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 11 Jul 2023 13:10:39 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230706T060000Z Message-ID: Sanity Test from 2023 July 10 (https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230706T060000Z/outputs/iso/starlingx-intel-x86-64-cd.iso) Status: GREEN SX sanity Passed: 17 (100.0%) Failed: 0 (0.0%) Total Executed: 17 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_2p_2_big_pod_best_effort_HT_AIO PASS test_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_mixed_add_vf_interface[1] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] DX sanity Passed: 19 (100.0%) Failed: 0 (0.0%) Total Executed: 19 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_swact_controller_platform PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_push_docker_image_to_local_registry_standby PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] PASS test_bmc_verify_bm_type_ipmi PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Michel.Thebeau at windriver.com Tue Jul 11 13:18:03 2023 From: Michel.Thebeau at windriver.com (Thebeau, Michel) Date: Tue, 11 Jul 2023 13:18:03 +0000 Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization In-Reply-To: References: Message-ID: Thanks for the feedback, the new story is here: https://storyboard.openstack.org/#!/story/2010816 Henry Bailey and I will be working through it. M ________________________________ From: Thebeau, Michel Sent: 10 July 2023 9:48 AM To: Waines, Greg ; starlingx-discuss at lists.starlingx.io Cc: Balaraj, Juanita ; Stone, Ronald Subject: Re: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Hi Greg, Yes, that's the example for aio-simplex specifically. I would have referred to the parent page which links to each deployment option: https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html Each of the listed deployment options under "Install StarlingX Kubernetes in a virtual environment" has the instruction for libvirt method. Yes, I am saying that I am intending that the changes should not impact anything that a user would do currently. I want to add options to better use a host's resources for disk, memory and CPU without affecting the current examples and default behaviour presented in the Starlingx documentation (and the libvirt method's README) M ________________________________ From: Waines, Greg Sent: 10 July 2023 9:21 AM To: Thebeau, Michel ; starlingx-discuss at lists.starlingx.io Cc: Balaraj, Juanita ; Stone, Ronald Subject: RE: Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Where is the ?libvirt virtual deployment method? documented under docs.starlingx.io ? Is it here ? https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_environ.html ( and corresponding spots for other configs ) So you?re saying your changes won?t impact the current documentation of the ?libvirt virtual deployment method? ? Greg. From: Thebeau, Michel Sent: Monday, July 10, 2023 8:55 AM To: Waines, Greg ; starlingx-discuss at lists.starlingx.io Cc: Balaraj, Juanita ; Stone, Ronald Subject: Re: Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Good morning Greg, Thanks for letting me know. I was not aware that the documents were out-of-sync and that the examples under virtual deployment were out-of-date. Especially: I had not noticed any out-of-date instruction while using the examples from virtual section. To answer your first question: I have an intention of not impacting the canonical examples and current usage/use-case. In this way I did not anticipate documentation changes. I especially intend that if one were using the libvirt deployment method as it is presented today, then the changes I intend would have no impact on that usage. I am not prepared to accept the assignment this morning. I can, for example, contribute to ensuring that a merging of the documents will continue to accurately reflect the libvirt virtual deployment method - either by proposing changes or reviewing the changes. Please feel free to bring me into the conversation. M ________________________________ From: Waines, Greg > Sent: 10 July 2023 8:24 AM To: Thebeau, Michel >; starlingx-discuss at lists.starlingx.io > Cc: Balaraj, Juanita >; Stone, Ronald > Subject: RE: Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Hey Mich, Thanksfor looking at this. Do you intent to update the virtual install guides as well ? ? as part of this work ? e.g. https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_install_kubernetes.html A heads up if you do ? (I think I?ve mentioned this a couple of times) * The bare-metal install guides have been enhanced/updated and maintained over the last few stx releases * ? but the virtual install guides have not * E.g. if you compare * https://docs.starlingx.io/deploy_install_guides/release/bare_metal/aio_simplex_install_kubernetes.html * And * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex.html * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_environ.html * https://docs.starlingx.io/deploy_install_guides/release/virtual/aio_simplex_install_kubernetes.html you?ll see several differences that are not necessarily due virtual versus bare-metal. * We (doc team) did not maintain the virtual install guides because we were thinking that * It was too much overhead maintaining both guides, * Instead we were going to combine the guides * And just have in the very few places, the difference between virtual versus bare-metal * BUT ? we have not had time to look at this. * * If you are interested in doing this ? let me, Juanita and Ron know and we can provide some guidance here. Greg. From: Thebeau, Michel > Sent: Wednesday, June 28, 2023 3:51 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization Hi, I prepared the following description of enhancements I intend towards the libvirt virtual deployment method. Please let me know I should follow a particular procedure. Otherwise I intend to create a story in storyboard. Mitch. === Starlingx Libvirt deployment method host utilization enhancements References: "Install StarlingX Kubernetes in a virtual environment" - https://docs.starlingx.io/deploy_install_guides/release/index-install-r7-8966076f0e81.html#index-install-r7-8966076f0e81 Libvirt deployment method in starlingx/tools - https://opendev.org/starlingx/tools/src/branch/master/deployment/libvirt Libvirt deployment method moved this week to starlingx/virtual-deployment - https://opendev.org/starlingx/virtual-deployment/src/branch/master/libvirt Motivation is to: A) maintain attributes for more than one virtual lab B) improve the usage and selection of the host's resources for disk, memory and cpu C) isolate cluster networks where more than one virtual lab may be running Philosophy of continuity: Introduce changes and developments in continuity with established examples and approaches. - Maintain the existing examples for default setting and the 'mad' override. - Establish regression test based on the default setting and 'mad' override to ensure that a user of the deployment method can continue to do the same thing they used to do. - Maintain and extend the use of overridable variable definitions for the attributes of a lab. - Maintain and extend the use of command line parameters for configuration selection, such as "-c 'simplex'". - Maintain and extend the existing workflow: "exporting variables, setup_network.sh, setup_configation.sh, destroy_configuration.sh, destroy_network.sh". A) Maintain configurations for more than one virtual cluster: Motivation: allow a lab's attributes to be recalled from a configuration file and operate upon that lab specifically. Establish a precedent for a configuration file used to override the default attributes. Refer to the README.rst "Overview" section which lists environment variables CONTROLLER, WORKER, BRIDGE_INTERFACE, EXTERNAL_NETWORK, EXTERNAL_IP. Provide a default configuration file that will reset the variables to defaults as they currently exist within the deployment/libvirt scripts, including: BRIDGE_INTERFACE=${BRIDGE_INTERFACE:-stxbr} EXTERNAL_NETWORK=${EXTERNAL_NETWORK:-10.10.10.0/24} EXTERNAL_IP=${EXTERNAL_IP:-10.10.10.1/24} CONFIGURATION=${CONFIGURATION:-simplex} CONTROLLER=${CONTROLLER:-controller} WORKER=${WORKER:-worker} STORAGE=${STORAGE:-storage} WORKER_NODES_NUMBER=${WORKER_NODES_NUMBER:-1} STORAGE_NODES_NUMBER=${STORAGE_NODES_NUMBER:-1} Provide an example configuration file that sets a lab's attributes deviating from the default. Especially, the default and the example should co-exist. Consider honouring the "mad" example in README.rst. If necessary provide an option to select values, or a script to set variables, from that configuration file. B) Improve usage and selection of host's resources: Motivation: allow lab specific attributes for the host's resources and provide tools to inspect those resources within the contexts of the virtual labs and/or overall Note: Ensure that all changes are providing defaults that are equivalent to the existing implementation. Values to add to the lab's attributes: Add DOMAIN_DIRECTORY to the set of overridable variables Add an override variable for the DISK file location for each node in a virtual lab. (currently hardcoded /var/lib/libvirt/images in functions.sh) Add an override variable for the MEMORY setting for each node (currently XML hardcoded ) Add an override variable for the CPU setting of each node (currently XML hardcoded ) Add scripting to assist with supervising the host's resources, such as: - listing the lab's nodes and networks; - inspecting the lab's network configurations; - inspecting the host's and lab's disk usage per configured disk; - listing a lab's nodes' cpu and memory allocations C) Isolate cluster networks where more than one cluster may be running: Motivation: on a host that has a capacity to run virtual clusters, ensure that there is no networking crosstalk between the running clusters. Provide scripting to add/remove iptables restrictions for a lab's networks. Initially assume no inter-cluster communication, and only the OAM network will route to external networks. Include: - ipv4 and/or ipv6 - a lab specific iptables CHAIN Probably: omit running this script automatically, since it changes the deployment behaviour. Consider adding an optional parameter to setup_network.sh. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Rob.Cooke at windriver.com Tue Jul 11 15:49:44 2023 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Tue, 11 Jul 2023 15:49:44 +0000 Subject: [Starlingx-discuss] Minutes: Test Status Call - July 11, 2023 Message-ID: Hi everyone, Please find below the minutes from this week's StarlingX Test Status Call: Minutes for 07/11/2023 * Open Topics: * Test meetings have resumed their weekly cadence, Tuesday's 8:00am Pacific, see this page for meeting details: * https://wiki.openstack.org/wiki/Starlingx/Meetings#8:00am_Pacific_-_Test_Team_Call * There was also a discussion that the feature list for STX9.0 may need to be revisited, to be discussed in the next release call * Sanity Status: * Sanity on STX 9.0 - Green * Last execution, July 10, 2023 - Results email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014273.html * Sanity on STX 9.0 plus Openstack - Green * Last execution, June 25, 2023 - Results email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014237.html * There is a run in progress today, expect to see results by Wednesday * Feature Test Status: * Feature testing is tracked in the following google sheet: * https://docs.google.com/spreadsheets/d/1El3g0ute5K2S5DTR9p_rxa1jQlq8gcUzgMCNCE_sx8g/edit#gid=968103774 * Some features are in progress * Regression Testing will be tracked here closer to release end: * https://docs.google.com/spreadsheets/d/1NjYk9N0whK91nHViB5HFG2C1-XdJ09StVuLMxsz0KAY/edit?pli=1#gid=1717644237 Thanks, Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lucas.DeAtaidesBarreto at windriver.com Tue Jul 11 18:57:16 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Tue, 11 Jul 2023 18:57:16 +0000 Subject: [Starlingx-discuss] Sanity and Regression - StarlingX + STX-Openstack MASTER build [20230706T060000Z] results - Jul - 11 Message-ID: Hi all, StarlingX + STX-Openstack sanity and regression results: Overall Status: GREEN Build Info: Build date: July 06 - 20230706T060000Z ISO: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230706T060000Z/outputs/iso/starlingx-intel-x86-64-20230706174736-cd.iso Helm Chart: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230706T060000Z/outputs/helm-charts/stx-openstack-1.0-1.stx.55-debian-stable-versioned.tgz AIO-DX Baremetal with VSWITCH_TYPE=OVS Sanity Results: Overall Status: GREEN Automated Test Results Summary: ------------------------------------------------------ Passed: 15 (100.00%) Failed: 0 (0.00%) Total Executed: 15 List of Test Cases: ------------------------------------------------------ PASS????20230711 13:08:38??????test_ssh_to_hosts PASS????20230711 13:10:00??????test_lock_unlock_host PASS????20230711 13:29:38??????test_openstack_services_healthy PASS????20230711 13:30:42??????test_reapply_stx_openstack_no_change[controller-0] PASS????20230711 13:32:39??????test_reapply_stx_openstack_no_change[controller-1] PASS????20230711 13:37:11??????test_horizon_create_delete_instance PASS????20230711 13:39:47??????test_swact_controllers PASS????20230711 13:47:36??????test_ping_between_two_vms[tis-centos-guest-virtio-virtio] PASS????20230711 13:54:22??????test_migrate_vm[tis-centos-guest-live-None] PASS????20230711 13:59:20??????test_nova_actions[tis-centos-guest-dedicated-pause-unpause] PASS????20230711 14:03:57??????test_nova_actions[tis-centos-guest-dedicated-suspend-resume] PASS????20230711 14:08:27??????test_evacuate_vms PASS????20230711 14:20:16??????test_system_coredumps_and_crashes[core_dumps] PASS????20230711 14:20:31??????test_system_coredumps_and_crashes[crash_reports] PASS????20230711 14:20:37??????test_system_alarms ----------------------------------------------------------------------- There is a Launchpad open for the test_reapply_stx_openstack_no_change[controller-1] test case: Bug #2023657: STX-O | config-out-of-date alarm won't disappear on controller-1 after swact and reapplying app. This test case is passing on a re-run. Regression Results: Overall Status: GREEN Automated Test Results Summary: ------------------------------------------------------ Passed: 12 (100.00%) Failed: 0 (0.00%) Total Executed: 12 List of Test Cases: ------------------------------------------------------ PASS????20230711 03:24:37??????test_lldp_neighbor_remote_port PASS????20230711 03:25:48??????test_kernel_module_signatures PASS????20230711 03:26:39??????test_delete_heat_after_swact[OS_Cinder_Volume.yaml] PASS????20230711 03:31:10??????test_multiports_on_same_network_vm_actions[virtio_x4] PASS????20230711 03:53:30??????test_cpu_pol_vm_actions[2-dedicated-image-volume] PASS????20230711 04:07:14??????test_vm_mem_pool_default_config[2048] PASS????20230711 04:10:52??????test_vm_mem_pool_default_config[1048576] PASS????20230711 04:17:12??????test_resize_vm_positive[local_image-4_1_512-5_2_1024-image] PASS????20230711 04:28:09??????test_server_group_boot_vms[affinity-2] PASS????20230711 04:34:34??????test_server_group_boot_vms[anti_affinity-2] PASS????20230711 04:41:18??????test_vm_with_config_drive PASS????20230711 05:05:12??????test_lock_with_vms ----------------------------------------------------------------------- Thanks, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Tue Jul 11 20:51:02 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Tue, 11 Jul 2023 13:51:02 -0700 Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility Message-ID: Hi StarlingX Community, The StarlingX project has been gaining new users and contributors lately, and the community already started to look into providing more on-boarding related materials and help people to find their ways around. Related to the above, I wanted to bring up the project?s Vulnerability Management guidelines. While there is some documentation available on the StarlingX wiki[1] currently, it is not the easiest to find. As this is a crucial area, I think it would be a good time to both make sure that the information there is up to date, as well as to make the documentation easier to find. Would it make sense to move the content of the aforementioned wiki over to the Documentation website? Regardless of where the information lives, where do you think would be good to add pointers to it, ie. the project?s homepage, the docs homepage, etc? Best Regards, Ildik? [1] https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation From Greg.Waines at windriver.com Wed Jul 12 11:49:20 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 12 Jul 2023 11:49:20 +0000 Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility In-Reply-To: References: Message-ID: We do have a high level view of 'CVE Maintenance' in docs.starlingx.io . https://docs.starlingx.io/security/kubernetes/cve-maintenance-723cd9dd54b3.html We could provide a reference/link here to the more detailed page in the wiki . Greg. -----Original Message----- From: Ildiko Vancsa Sent: Tuesday, July 11, 2023 4:51 PM To: StarlingX ML Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, The StarlingX project has been gaining new users and contributors lately, and the community already started to look into providing more on-boarding related materials and help people to find their ways around. Related to the above, I wanted to bring up the project?s Vulnerability Management guidelines. While there is some documentation available on the StarlingX wiki[1] currently, it is not the easiest to find. As this is a crucial area, I think it would be a good time to both make sure that the information there is up to date, as well as to make the documentation easier to find. Would it make sense to move the content of the aforementioned wiki over to the Documentation website? Regardless of where the information lives, where do you think would be good to add pointers to it, ie. the project?s homepage, the docs homepage, etc? Best Regards, Ildik? [1] https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io From fungi at yuggoth.org Wed Jul 12 13:26:43 2023 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 12 Jul 2023 13:26:43 +0000 Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility In-Reply-To: References: Message-ID: <20230712132643.fmhxnrtzphvwyzwr@yuggoth.org> On 2023-07-11 13:51:02 -0700 (-0700), Ildiko Vancsa wrote: [...] > Related to the above, I wanted to bring up the project?s > Vulnerability Management guidelines. While there is some > documentation available on the StarlingX wiki[1] currently, it is > not the easiest to find. As this is a crucial area, I think it > would be a good time to both make sure that the information there > is up to date, as well as to make the documentation easier to > find. [...] The main thing I worry about is users not being able to easily find instructions for how the StarlingX maintainers want them to report suspected security vulnerabilities. Some may guess, and may guess poorly, others may give up looking and just disclose it in public. This could result in a (preventable) scramble for everyone trying to deal with the results of those choices. Taking OpenStack as an example, in the footer of every page on openstack.org and related sites there's a "Security" link which goes to a dedicated documentation page about security topics (it uses a different subdomain than the project or docs sites but that's more of a historical implementation detail, if I were redoing it today I'd want to merge all the sites into one). At the very top of that security page is a section[*] which describes in detail how users should safely notify the maintainers of suspected vulnerabilities. Zuul has a similar page[**], linked from the main project documentation TOC (linking to it from more places would probably be a good idea as a future improvement). Once you have a security page, it can also become a convenient place to list your recent security advisories/patches, link to existing vulnerability management process documents, and potentially talk about security-specific features of StarlingX or security-relevant efforts within the StarlingX community as a sort of rallying point. [*] https://security.openstack.org/#how-to-report-security-issues-to-openstack [**] https://zuul-ci.org/docs/zuul/latest/vulnerabilities.html -- 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 starlingx.build at gmail.com Wed Jul 12 15:17:40 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 12 Jul 2023 11:17:40 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_debian_master - Build # 221 - Failure! Message-ID: <1880208039.58.1689175061579.JavaMail.javamailuser@localhost> Project: STX_build_debian_master Build #: 221 Status: Failure Timestamp: 20230712T060000Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230712T060000Z/logs -------------------------------------------------------------------------------- Parameters BUILD_PACKAGES_LIST: CLEAN_DOWNLOADS: false BUILD_HELM_CHARTS: true USE_DOCKER_CACHE: true DOCKER_IMAGE_LIST: PUSH_DOCKER_IMAGES: true CLEAN_DOCKER: true REFRESH_SOURCE: true DRY_RUN: false CLEAN_PACKAGES: true BUILD_RT: true BUILD_PACKAGES: true CLEAN_REPOMGR: true PKG_REUSE: false JENKINS_SCRIPTS_BRANCH: master BUILD_DOCKER_BASE_IMAGE: true BUILD_DOCKER_IMAGES: true FORCE_BUILD: false REBUILD_BUILDER_IMAGES: true CLEAN_ISO: true BUILD_ISO: true From ildiko at openinfra.dev Wed Jul 12 22:35:14 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 12 Jul 2023 15:35:14 -0700 Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility In-Reply-To: References: Message-ID: <617AF541-97DB-455A-A267-DA472F2B1B0B@openinfra.dev> Hi Greg, Thank you for sharing that pointer. There are multiple aspects to security and vulnerability related features, activities and actions. The documentation website mainly covers the features in the platform. In addition, the page that you shared also talks about the CVE scan process and briefly mentions the security team. I think it is great to have documentation available about the CVE scans. At the same time, the placement of the link to the page makes it a little hidden in the list of related features in the platform. The page also says that ?the master development branch of StarlingX is scanned for CVEs? and does not say anything about Kubernetes in particular, however, it is listed under a Kubernetes section. Is there a specific reason for that? I think it would be great to separate the features from the activities, including what users can do if they identify a vulnerability issue. And make that information much more visible and easy to find. We can also add the CVE scan related information there. What do you think? Thanks, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 12, 2023, at 04:49, Waines, Greg wrote: > > We do have a high level view of 'CVE Maintenance' in docs.starlingx.io . > https://docs.starlingx.io/security/kubernetes/cve-maintenance-723cd9dd54b3.html > We could provide a reference/link here to the more detailed page in the wiki . > > Greg. > > -----Original Message----- > From: Ildiko Vancsa > Sent: Tuesday, July 11, 2023 4:51 PM > To: StarlingX ML > Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility > > CAUTION: This email comes from a non Wind River email account! > Do not click links or open attachments unless you recognize the sender and know the content is safe. > > Hi StarlingX Community, > > The StarlingX project has been gaining new users and contributors lately, and the community already started to look into providing more on-boarding related materials and help people to find their ways around. > > Related to the above, I wanted to bring up the project?s Vulnerability Management guidelines. While there is some documentation available on the StarlingX wiki[1] currently, it is not the easiest to find. As this is a crucial area, I think it would be a good time to both make sure that the information there is up to date, as well as to make the documentation easier to find. > > Would it make sense to move the content of the aforementioned wiki over to the Documentation website? Regardless of where the information lives, where do you think would be good to add pointers to it, ie. the project?s homepage, the docs homepage, etc? > > Best Regards, > Ildik? > > [1] https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management > > ??? > > Ildik? V?ncsa > Director of Community > Open Infrastructure Foundation > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From Ghada.Khalil at windriver.com Wed Jul 12 23:13:22 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 12 Jul 2023 23:13:22 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Jul 12, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call July 12, 2023 Standing topics - Build - Main Branch Debian Builds - Green - Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/ - stx.6.0 Weekly RC Builds - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/ - stx.7.0 Weekly RC Builds - Green - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/ - Note: No container image builds are done for stx.7.0 - stx.8.0 Weekly RC Builds - Green - Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/ - Transition from CENGN - Build team is working on transitioning the builds to WR infrastructure as CENGN will no longer be able to host the StarlingX builds. - Timing: Tentatively end-July / early-Aug - Status: - Able to build everything now - Still working w/ WR IT on publicly posting build results, but making progress and should have an update next week. - Sanity - Debian Main Branch Platform Sanity - Last sanity email sent on July 11: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014273.html - Status: Green for SX and DX - Debian Main Branch stx-openstack Sanity - Last sanity email sent on July 11: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014276.html - Status: Green - Gerrit Reviews in Need of Attention - No Gerrit reviews needing discussion this week. - From previous meetings: Fixes to libvirt env: https://review.opendev.org/c/starlingx/tools/+/863735 - Abandoned as the tools repo has been restructured. - Reference Links: - Active Branch (open): https://review.opendev.org/q/projects:starlingx+is:open+branch:+master - Active Branch (merged): https://review.opendev.org/q/projects:starlingx+is:merged+branch:master Topics for this week - Ghada away next week. Greg will chair the community call. ARs from Previous Meetings - Manifest repo re-configuration / split to allow stx-openstack to be built independently from the platform - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014206.html - No concerns from the community regarding this proposal. - The key issue is scheduling time for the build team to implement the change. - Action: Build team to propose a timeline based on their priorities/availability. - Build Team planning on end-of-July ... after CENGN work complete - StoryBoard tracking the work: https://storyboard.openstack.org/#!/story/2010797 - Renaming App Repos to remove the "armada" - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014215.html - Minor / cosmetic change. Lower priority, but would be nice to do. Should have no impact on runtime. - Action: Build team to propose a timeline based on their priorities/availability. (lower priority than the manifest repo re-config) - Still planning ... likely after splitting manifests for openstack - StarlingX Subproject Meetings Update - Action: Scott Little to confirm w/ Mike Matteson on the build meeings - Scott is suggesting to cover build topics as part of the OS-distro meeting. Scott to discuss with the PL/TL. - Status: see below ( Part of Greg's followup with subprojects' meeting schedules ) - Action: Chris Friesen to provide an update on the containerization meetings - Status: see below ( Part of Greg's followup with subprojects' meeting schedules ) - Action: Greg ... Review which subproject teams are holding meetings on regular basis in StarlingX environment - Status: Closed / Greg followed up; only the build & container subproject teams doing have regular meetings. Bruce & Greg are following up. - ARM Support - Action: Scott Kamp to respond to Jackie/the mailing list to provide assistance/access to some arm machines - Action: Scott Little to respond regarding build questions - Cannot mirror more files on CENGN; will need to wait until we transition away from CENGN - Action: Scott Kamp to explore providing a hosting env temporarily - No plan to publish images to dockerhub/starlingx until they are part of the official build infrastructure - Under discussion in the OS subproject meeting - Jackie is donating hardware, but it needs to be managed by someone - Status: Open / No Update - Greg took the action to identify the right prime to drive the ARM Support project within StarlingX - SteveG available to help Open Requests for Help - Help w/ Install - Two people asking for help with installation on IRC - Bruno is trying to help them, but it appears that they are in a different timezone. If others can participate, it would be great. - Switch of Activity - Email thread: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014260.html - Status: - Already answered by Greg on July 10. Will leave open for another week in case there is further response from the reporter - Issue w/ pxebooting a second node on StarlingX - Question raised on the community call (Apr 26) by Kevin - The initial node installs/boots correctly, but but an identical second node doesn't. This setup is using vmare to run StarlingX in VMs. - Status: Open / Greg has some information to share, but isn't sure how to get in touch w/ Kevin - Build System Setup - Question was posted on IRC by Kevin - StarlingX documentation has a lot of outdated information. It took a lot of digging to find the right documentation for setting up a build env with minikube. - Requested that Kevin open an LP to the doc team and/or send an email to the mailing list w/ more details to the mailing list - Status: Open / No email sent to the mailing list yet. Unsure if LP was opened. - Support for StarlingX 8 setup bring up - Reported by Prashanthi - Email thread: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/014026.html - Status: - Open / Discussion is active on the mailing list. Greg providing assistance. The issues are related to date/time issues on servers being setup as well as firewall issues - CURRENTLY PAUSED ... Prashanthi had higher internal priorities that have taken her away from looking at StarlingX for the time being; waiting for Prashanthi to get back to us. From ildiko at openinfra.dev Wed Jul 12 23:14:07 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Wed, 12 Jul 2023 16:14:07 -0700 Subject: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED In-Reply-To: References: Message-ID: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> Hi, Thank you all for the feedback so far! I haven?t received any objections against the option to start using Matrix as a chat tool for the StarlingX community. People had questions on the Community Call about the tool today, so I collected some useful information to help exploring it: - As a reminder, you can find out more about the tool here: https://matrix.org - There are different options to use as a browser or desktop client. Many of them are also available on smartphones. + I?m using Element - https://element.io + Some other options include ~ Weechat - https://github.com/poljar/weechat-matrix ~ SchildiChat - https://schildi.chat/ ~ FluffyChat - https://fluffychat.im/ - The #starlingX IRC channel is also available through Matrix - https://matrix.to/#/!XDOJNehPiaWKvYGWVD:matrix.org?via=matrix.org ~ You will need to create an account first ~ There is documentation available in the Zuul community?s docs about how to register - https://zuul-ci.org/docs/zuul/latest/howtos/matrix.html#create-an-account During the Community Call, it also came up that it would be great to agree on how we would like to utilize a chat tool. For instance, to aovid having too many channels, etc. The current proposal to the Matrix setup is the following: - Have multiple chat rooms available for community communication: + starlingx-general room - topics that are relevant to the whole community + StarlingX project team channels ~ topics that are relevant to a project team ~ ie: starlingx-build, starlingx-containers, etc + Optional channel ideas - specific topic areas that are outside of the existing project teams ~ starlingx-newcomers ~ starlingx-troubleshooting __ If you are in support to use Matrix as the chat tool for StarlingX moving forward, please reply to this email with ?+1?.__ Please let me know if you have any questions, or if you need help with setting up Matrix. Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 4, 2023, at 21:42, open infra wrote: > > CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord. > Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply). > > > > > > On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa wrote: > Hi StarlingX Community, > > I?m reaching out to you about a recurring topic that came up during the PTG last week again. > > While the community is actively using the mailing list, it is not always the best platform, as it doesn?t allow for more synchronous chat. Contributors at the event had a growing interest in finding a way to provide the opportunity for more synchronous communication to capture the project teams? chatters, and enable newcomers to reach out and start to participate. > > Challenges: > * Tooling: People raised that while it is an open protocol, IRC still doesn?t feel inclusive due to its simplicity. > * Format: The current one-channel setup doesn?t feel efficient and comfortable, since people need to address everyone in the channel with every topic they have a question or comment about. > > > Proposal to move forward: > * Tooling: The preferred tool in last week?s conversation was Matrix - https://matrix.org > - It is an open tool, which ensures continued access to the platform and its features > - It is more modern than IRC > > * Format: The idea came up to create multiple channels for the StarlingX project > - We can keep the all-community channel > - We can create channels for each project team, that are more topic specific > - We also have the option to create a channel for newcomers, which could include troubleshooting type of conversations as well > > > In order to identify next steps, please share your feedback about the proposal above. Ie: What do you think about Matrix? Would you be more comfortable using a chat tool with the more fine grained configuration of having multiple channels? > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Director of Community > Open Infrastructure Foundation > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From scott.kamp at xunison.com Wed Jul 12 23:19:48 2023 From: scott.kamp at xunison.com (Scott Kamp) Date: Wed, 12 Jul 2023 23:19:48 +0000 Subject: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED In-Reply-To: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> References: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> Message-ID: +1 Get Outlook for Android ________________________________ From: Ildiko Vancsa Sent: Thursday, July 13, 2023 6:14:07 AM To: StarlingX ML Subject: Re: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED Hi, Thank you all for the feedback so far! I haven?t received any objections against the option to start using Matrix as a chat tool for the StarlingX community. People had questions on the Community Call about the tool today, so I collected some useful information to help exploring it: - As a reminder, you can find out more about the tool here: https://matrix.org - There are different options to use as a browser or desktop client. Many of them are also available on smartphones. + I?m using Element - https://element.io + Some other options include ~ Weechat - https://github.com/poljar/weechat-matrix ~ SchildiChat - https://schildi.chat/ ~ FluffyChat - https://fluffychat.im/ - The #starlingX IRC channel is also available through Matrix - https://matrix.to/#/!XDOJNehPiaWKvYGWVD:matrix.org?via=matrix.org ~ You will need to create an account first ~ There is documentation available in the Zuul community?s docs about how to register - https://zuul-ci.org/docs/zuul/latest/howtos/matrix.html#create-an-account During the Community Call, it also came up that it would be great to agree on how we would like to utilize a chat tool. For instance, to aovid having too many channels, etc. The current proposal to the Matrix setup is the following: - Have multiple chat rooms available for community communication: + starlingx-general room - topics that are relevant to the whole community + StarlingX project team channels ~ topics that are relevant to a project team ~ ie: starlingx-build, starlingx-containers, etc + Optional channel ideas - specific topic areas that are outside of the existing project teams ~ starlingx-newcomers ~ starlingx-troubleshooting __ If you are in support to use Matrix as the chat tool for StarlingX moving forward, please reply to this email with ?+1?.__ Please let me know if you have any questions, or if you need help with setting up Matrix. Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 4, 2023, at 21:42, open infra wrote: > > CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord. > Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply). > > > > > > On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa wrote: > Hi StarlingX Community, > > I?m reaching out to you about a recurring topic that came up during the PTG last week again. > > While the community is actively using the mailing list, it is not always the best platform, as it doesn?t allow for more synchronous chat. Contributors at the event had a growing interest in finding a way to provide the opportunity for more synchronous communication to capture the project teams? chatters, and enable newcomers to reach out and start to participate. > > Challenges: > * Tooling: People raised that while it is an open protocol, IRC still doesn?t feel inclusive due to its simplicity. > * Format: The current one-channel setup doesn?t feel efficient and comfortable, since people need to address everyone in the channel with every topic they have a question or comment about. > > > Proposal to move forward: > * Tooling: The preferred tool in last week?s conversation was Matrix - https://matrix.org > - It is an open tool, which ensures continued access to the platform and its features > - It is more modern than IRC > > * Format: The idea came up to create multiple channels for the StarlingX project > - We can keep the all-community channel > - We can create channels for each project team, that are more topic specific > - We also have the option to create a channel for newcomers, which could include troubleshooting type of conversations as well > > > In order to identify next steps, please share your feedback about the proposal above. Ie: What do you think about Matrix? Would you be more comfortable using a chat tool with the more fine grained configuration of having multiple channels? > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Director of Community > Open Infrastructure Foundation > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Greg.Waines at windriver.com Thu Jul 13 11:30:43 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 13 Jul 2023 11:30:43 +0000 Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility In-Reply-To: <617AF541-97DB-455A-A267-DA472F2B1B0B@openinfra.dev> References: <617AF541-97DB-455A-A267-DA472F2B1B0B@openinfra.dev> Message-ID: Are you thinking of keeping the security 'activities/actions' in the wiki and the security 'features' in the doc site ? ... i'm fine with that. Wrt your question about 'Kubernetes' ... - you'll notice that MANY of the top-level sections in the doc site have 2x major sub-sections: Kubernetes and OpenStack - this was done to split the topics related to * the Kubernetes Platform and * the OpenStack Application - So the 'Kubernetes' reference is really a reference to the Platform Wrt to making this info (i.e. https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ) more visible. Currently it requires you to navigate as follows: - StarlingX WIKI https://wiki.openstack.org/wiki/StarlingX - StarlingX sub-projects > Security project https://wiki.openstack.org/wiki/StarlingX/Security - Select 'Vulnerability Management Process' https://wiki.openstack.org/wiki/StarlingX/Security#Vulnerability_Management_Process - Select ' See https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ' We could put an additional direct link to it higher in the WIKI - maybe under 'Planning & Processes' Thoughts ? Greg. -----Original Message----- From: Ildiko Vancsa Sent: Wednesday, July 12, 2023 6:35 PM To: Waines, Greg Cc: StarlingX ML Subject: Re: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi Greg, Thank you for sharing that pointer. There are multiple aspects to security and vulnerability related features, activities and actions. The documentation website mainly covers the features in the platform. In addition, the page that you shared also talks about the CVE scan process and briefly mentions the security team. I think it is great to have documentation available about the CVE scans. At the same time, the placement of the link to the page makes it a little hidden in the list of related features in the platform. The page also says that ?the master development branch of StarlingX is scanned for CVEs? and does not say anything about Kubernetes in particular, however, it is listed under a Kubernetes section. Is there a specific reason for that? I think it would be great to separate the features from the activities, including what users can do if they identify a vulnerability issue. And make that information much more visible and easy to find. We can also add the CVE scan related information there. What do you think? Thanks, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 12, 2023, at 04:49, Waines, Greg wrote: > > We do have a high level view of 'CVE Maintenance' in docs.starlingx.io . > https://docs.starlingx.io/security/kubernetes/cve-maintenance-723cd9dd > 54b3.html We could provide a reference/link here to the more detailed > page in the wiki . > > Greg. > > -----Original Message----- > From: Ildiko Vancsa > Sent: Tuesday, July 11, 2023 4:51 PM > To: StarlingX ML > Subject: [Starlingx-discuss] Vulnerability Management guidelines - > improving visibility > > CAUTION: This email comes from a non Wind River email account! > Do not click links or open attachments unless you recognize the sender and know the content is safe. > > Hi StarlingX Community, > > The StarlingX project has been gaining new users and contributors lately, and the community already started to look into providing more on-boarding related materials and help people to find their ways around. > > Related to the above, I wanted to bring up the project?s Vulnerability Management guidelines. While there is some documentation available on the StarlingX wiki[1] currently, it is not the easiest to find. As this is a crucial area, I think it would be a good time to both make sure that the information there is up to date, as well as to make the documentation easier to find. > > Would it make sense to move the content of the aforementioned wiki over to the Documentation website? Regardless of where the information lives, where do you think would be good to add pointers to it, ie. the project?s homepage, the docs homepage, etc? > > Best Regards, > Ildik? > > [1] > https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Manag > ement > > ??? > > Ildik? V?ncsa > Director of Community > Open Infrastructure Foundation > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From fungi at yuggoth.org Thu Jul 13 11:55:06 2023 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 13 Jul 2023 11:55:06 +0000 Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility In-Reply-To: References: <617AF541-97DB-455A-A267-DA472F2B1B0B@openinfra.dev> Message-ID: <20230713115505.gepaob2fhbroxrk3@yuggoth.org> On 2023-07-13 11:30:43 +0000 (+0000), Waines, Greg wrote: [...] > Wrt to making this info (i.e. https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ) more visible. > Currently it requires you to navigate as follows: > - StarlingX WIKI https://wiki.openstack.org/wiki/StarlingX > - StarlingX sub-projects > Security project https://wiki.openstack.org/wiki/StarlingX/Security > - Select 'Vulnerability Management Process' https://wiki.openstack.org/wiki/StarlingX/Security#Vulnerability_Management_Process > - Select ' See https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ' > > We could put an additional direct link to it higher in the WIKI > - maybe under 'Planning & Processes' [...] I'm not sure your Vulnerability Management Process document is what needs increased visibility. Stepping back a bit, if I'm a StarlingX user who isn't well-connected with the contributor community and I find a misbehavior in the platform that I think might have security implications, I'll likely want to know how to safely report that to the StarlingX maintainers. I'm going to go to https://starlingx.io/ and start looking for information on how to report security issues. I'll keyword search for "security" on the main page of that project site and find that it appears twice, but associated with a link to a video about tamper resistance features, so that's not it. I'll maybe try searching for "vu..." nope nothing. Okay maybe it's on the FAQs page? No, not there either. In the docs? Oh hey look, there's a security section. Never mind, it's about more security features of the platform. I might eventually stumble on that kinda subtle link to the StarlingX wiki from the main documentation page and find the link there to the Security sub-project and then the https://wiki.openstack.org/wiki/StarlingX/Security#How_to_report_security_issues_to_StarlingX section therein, but it's also quite possible I will have given up before getting that far, or asked on a mailing list and naively disclosed some details of a vulnerability when doing so. My suggestion is to get a link to that Security sub-team page in the footers of everything on the starlingx.io and docs.starlingx.io sites. Keeping https://wiki.openstack.org/wiki/StarlingX/Security in a wiki page is fine if you don't think it's suitable to move into your docs repository (or to have a separate repository the Security sub-team can use for their publications), but I also recommend moving the bug reporting instructions farther up that page. Ideally it would be about the first thing someone sees when landing there (perhaps after a brief intro paragraph). -- 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 douglas.pereira at encora.com Thu Jul 13 12:05:52 2023 From: douglas.pereira at encora.com (Douglas Lopes Pereira) Date: Thu, 13 Jul 2023 12:05:52 +0000 Subject: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED In-Reply-To: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> References: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> Message-ID: +1 as long as we have a date to stop using IRC. Otherwise we will have to keep watching both messaging platforms. Douglas Lopes Pereira Software Development Manager M: +55 (19) 99212-3212 Campinas, BR [Encora] [We are proud to be recognized as Leaders in digital engineering services by Zinnov zones] ________________________________ From: Ildiko Vancsa Sent: Wednesday, July 12, 2023 8:14 PM To: StarlingX ML Subject: Re: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED External Mail: Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, Thank you all for the feedback so far! I haven?t received any objections against the option to start using Matrix as a chat tool for the StarlingX community. People had questions on the Community Call about the tool today, so I collected some useful information to help exploring it: - As a reminder, you can find out more about the tool here: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatrix.org%2F&data=05%7C01%7Cdouglas.pereira%40encora.com%7C8cde130bfb9d432264cc08db832e7b2d%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248007905555421%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=D49m6fzCXfQIfXwXfYIS5soeg%2BztwaA79tv3h9dxTGw%3D&reserved=0 - There are different options to use as a browser or desktop client. Many of them are also available on smartphones. + I?m using Element - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Felement.io%2F&data=05%7C01%7Cdouglas.pereira%40encora.com%7C8cde130bfb9d432264cc08db832e7b2d%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248007905555421%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0fOYxs0f5kviUFDsqiVOkOn5dBKyQQ7PQxiLHiDk9EU%3D&reserved=0 + Some other options include ~ Weechat - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpoljar%2Fweechat-matrix&data=05%7C01%7Cdouglas.pereira%40encora.com%7C8cde130bfb9d432264cc08db832e7b2d%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248007905555421%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=74gHLsZPLm%2BLOkmEwka5RIAi8QHxH4iueO1%2F3Ut6TOo%3D&reserved=0 ~ SchildiChat - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fschildi.chat%2F&data=05%7C01%7Cdouglas.pereira%40encora.com%7C8cde130bfb9d432264cc08db832e7b2d%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248007905555421%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=2toirOUtk8DD8mg5vsSy8xS%2FgDxELE1AwOlzbapuXSE%3D&reserved=0 ~ FluffyChat - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffluffychat.im%2F&data=05%7C01%7Cdouglas.pereira%40encora.com%7C8cde130bfb9d432264cc08db832e7b2d%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248007905555421%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VaddpohtfLmc3kdugAJGoDECmidvuduuXMSnIWCvoD4%3D&reserved=0 - The #starlingX IRC channel is also available through Matrix - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatrix.to%2F%23%2F!XDOJNehPiaWKvYGWVD%3Amatrix.org%3Fvia%3Dmatrix.org&data=05%7C01%7Cdouglas.pereira%40encora.com%7C8cde130bfb9d432264cc08db832e7b2d%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248007905555421%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2FP1ipjfdxTJmaPoqJVE2VSuwg%2FUORDqbxlw%2Bd6KG6Lk%3D&reserved=0 ~ You will need to create an account first ~ There is documentation available in the Zuul community?s docs about how to register - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzuul-ci.org%2Fdocs%2Fzuul%2Flatest%2Fhowtos%2Fmatrix.html%23create-an-account&data=05%7C01%7Cdouglas.pereira%40encora.com%7C8cde130bfb9d432264cc08db832e7b2d%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248007905555421%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=t54aPFcB6Ca6iSf5xAezP3pcpo4yhV7TnbXmB9RJlHg%3D&reserved=0 During the Community Call, it also came up that it would be great to agree on how we would like to utilize a chat tool. For instance, to aovid having too many channels, etc. The current proposal to the Matrix setup is the following: - Have multiple chat rooms available for community communication: + starlingx-general room - topics that are relevant to the whole community + StarlingX project team channels ~ topics that are relevant to a project team ~ ie: starlingx-build, starlingx-containers, etc + Optional channel ideas - specific topic areas that are outside of the existing project teams ~ starlingx-newcomers ~ starlingx-troubleshooting __ If you are in support to use Matrix as the chat tool for StarlingX moving forward, please reply to this email with ?+1?.__ Please let me know if you have any questions, or if you need help with setting up Matrix. Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 4, 2023, at 21:42, open infra wrote: > > CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord. > Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply). > > > > > > On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa wrote: > Hi StarlingX Community, > > I?m reaching out to you about a recurring topic that came up during the PTG last week again. > > While the community is actively using the mailing list, it is not always the best platform, as it doesn?t allow for more synchronous chat. Contributors at the event had a growing interest in finding a way to provide the opportunity for more synchronous communication to capture the project teams? chatters, and enable newcomers to reach out and start to participate. > > Challenges: > * Tooling: People raised that while it is an open protocol, IRC still doesn?t feel inclusive due to its simplicity. > * Format: The current one-channel setup doesn?t feel efficient and comfortable, since people need to address everyone in the channel with every topic they have a question or comment about. > > > Proposal to move forward: > * Tooling: The preferred tool in last week?s conversation was Matrix - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatrix.org%2F&data=05%7C01%7Cdouglas.pereira%40encora.com%7C8cde130bfb9d432264cc08db832e7b2d%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248007905555421%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=D49m6fzCXfQIfXwXfYIS5soeg%2BztwaA79tv3h9dxTGw%3D&reserved=0 > - It is an open tool, which ensures continued access to the platform and its features > - It is more modern than IRC > > * Format: The idea came up to create multiple channels for the StarlingX project > - We can keep the all-community channel > - We can create channels for each project team, that are more topic specific > - We also have the option to create a channel for newcomers, which could include troubleshooting type of conversations as well > > > In order to identify next steps, please share your feedback about the proposal above. Ie: What do you think about Matrix? Would you be more comfortable using a chat tool with the more fine grained configuration of having multiple channels? > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Director of Community > Open Infrastructure Foundation > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Thu Jul 13 12:39:00 2023 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 13 Jul 2023 12:39:00 +0000 Subject: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED In-Reply-To: References: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> Message-ID: <20230713123900.yasnws7wgteaqy37@yuggoth.org> On 2023-07-13 12:05:52 +0000 (+0000), Douglas Lopes Pereira wrote: > +1 as long as we have a date to stop using IRC. Otherwise we will > have to keep watching both messaging platforms. [...] As Ildiko mentioned, Matrix is bridged to a number of IRC networks, including OFTC where the current StarlingX channels reside. If they want, Matrix users can (for all intents and purposes) treat those as "just more Matrix channels." Matrix users get pretty much all the standard Matrix features when interacting on IRC channels through a bridge, while users who are in those channels via traditional IRC protocol can still interact with everyone there (albeit with a degraded feature set compared to using Matrix). I wouldn't recommend maintaining an official presence in the IRC channels after you complete a transition to Matrix, but it's still pretty easy for a handful of people to keep an eye on the old IRC channels through Matrix and try to help reroute newcomers who aren't aware you've moved. That's what the Zuul community did when it switched to Matrix a few years ago. -- 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 Bruno.Muniz at encora.com Thu Jul 13 12:46:19 2023 From: Bruno.Muniz at encora.com (Bruno Drugowick Muniz) Date: Thu, 13 Jul 2023 12:46:19 +0000 Subject: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED In-Reply-To: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> References: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> Message-ID: +1 ________________________________ From: Ildiko Vancsa Sent: Wednesday, July 12, 2023 20:14 To: StarlingX ML Subject: Re: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED External Mail: Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, Thank you all for the feedback so far! I haven?t received any objections against the option to start using Matrix as a chat tool for the StarlingX community. People had questions on the Community Call about the tool today, so I collected some useful information to help exploring it: - As a reminder, you can find out more about the tool here: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatrix.org%2F&data=05%7C01%7Cbruno.muniz%40encora.com%7Cdaf2b409b7404f8d020f08db832e25d0%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248006473007823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J6SMqIaBXd3qFzcwI97sKcQpEhCCq%2BvzbK44JfoF3vU%3D&reserved=0 - There are different options to use as a browser or desktop client. Many of them are also available on smartphones. + I?m using Element - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Felement.io%2F&data=05%7C01%7Cbruno.muniz%40encora.com%7Cdaf2b409b7404f8d020f08db832e25d0%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248006473007823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=oMIpD33WtcwgSuKAKJbt3N3vk5KukdFD%2FsSbtWj311I%3D&reserved=0 + Some other options include ~ Weechat - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpoljar%2Fweechat-matrix&data=05%7C01%7Cbruno.muniz%40encora.com%7Cdaf2b409b7404f8d020f08db832e25d0%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248006473007823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=RlX6s6akYJFJac%2FtEDuagXDLbS0Gh%2FLeEED1asIRGD4%3D&reserved=0 ~ SchildiChat - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fschildi.chat%2F&data=05%7C01%7Cbruno.muniz%40encora.com%7Cdaf2b409b7404f8d020f08db832e25d0%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248006473007823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Buba0PcDl1WJdtqqAiwxxjt5C8jmiUiQdOFLYuf39wk%3D&reserved=0 ~ FluffyChat - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffluffychat.im%2F&data=05%7C01%7Cbruno.muniz%40encora.com%7Cdaf2b409b7404f8d020f08db832e25d0%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248006473007823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=QYg7JoIDy2UEPnS3HYZMkhlTtej2kL0IJdN1ngB5fLw%3D&reserved=0 - The #starlingX IRC channel is also available through Matrix - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatrix.to%2F%23%2F!XDOJNehPiaWKvYGWVD%3Amatrix.org%3Fvia%3Dmatrix.org&data=05%7C01%7Cbruno.muniz%40encora.com%7Cdaf2b409b7404f8d020f08db832e25d0%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248006473007823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=JP%2Fy69h2B9ZzjD0Wz6gohdiqJ43CgzopjjgX3FFuN%2B4%3D&reserved=0 ~ You will need to create an account first ~ There is documentation available in the Zuul community?s docs about how to register - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzuul-ci.org%2Fdocs%2Fzuul%2Flatest%2Fhowtos%2Fmatrix.html%23create-an-account&data=05%7C01%7Cbruno.muniz%40encora.com%7Cdaf2b409b7404f8d020f08db832e25d0%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248006473007823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7YD%2F6EQKvsQp5YLBUSpQbqwucFnfj7ATr%2BAeG8%2BBQSE%3D&reserved=0 During the Community Call, it also came up that it would be great to agree on how we would like to utilize a chat tool. For instance, to aovid having too many channels, etc. The current proposal to the Matrix setup is the following: - Have multiple chat rooms available for community communication: + starlingx-general room - topics that are relevant to the whole community + StarlingX project team channels ~ topics that are relevant to a project team ~ ie: starlingx-build, starlingx-containers, etc + Optional channel ideas - specific topic areas that are outside of the existing project teams ~ starlingx-newcomers ~ starlingx-troubleshooting __ If you are in support to use Matrix as the chat tool for StarlingX moving forward, please reply to this email with ?+1?.__ Please let me know if you have any questions, or if you need help with setting up Matrix. Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 4, 2023, at 21:42, open infra wrote: > > CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord. > Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply). > > > > > > On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa wrote: > Hi StarlingX Community, > > I?m reaching out to you about a recurring topic that came up during the PTG last week again. > > While the community is actively using the mailing list, it is not always the best platform, as it doesn?t allow for more synchronous chat. Contributors at the event had a growing interest in finding a way to provide the opportunity for more synchronous communication to capture the project teams? chatters, and enable newcomers to reach out and start to participate. > > Challenges: > * Tooling: People raised that while it is an open protocol, IRC still doesn?t feel inclusive due to its simplicity. > * Format: The current one-channel setup doesn?t feel efficient and comfortable, since people need to address everyone in the channel with every topic they have a question or comment about. > > > Proposal to move forward: > * Tooling: The preferred tool in last week?s conversation was Matrix - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatrix.org%2F&data=05%7C01%7Cbruno.muniz%40encora.com%7Cdaf2b409b7404f8d020f08db832e25d0%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638248006473007823%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=J6SMqIaBXd3qFzcwI97sKcQpEhCCq%2BvzbK44JfoF3vU%3D&reserved=0 > - It is an open tool, which ensures continued access to the platform and its features > - It is more modern than IRC > > * Format: The idea came up to create multiple channels for the StarlingX project > - We can keep the all-community channel > - We can create channels for each project team, that are more topic specific > - We also have the option to create a channel for newcomers, which could include troubleshooting type of conversations as well > > > In order to identify next steps, please share your feedback about the proposal above. Ie: What do you think about Matrix? Would you be more comfortable using a chat tool with the more fine grained configuration of having multiple channels? > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Director of Community > Open Infrastructure Foundation > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Thu Jul 13 15:43:02 2023 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Thu, 13 Jul 2023 08:43:02 -0700 Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility In-Reply-To: <20230713115505.gepaob2fhbroxrk3@yuggoth.org> References: <617AF541-97DB-455A-A267-DA472F2B1B0B@openinfra.dev> <20230713115505.gepaob2fhbroxrk3@yuggoth.org> Message-ID: <1FAE18CB-B495-4E73-8D22-021ACCC7C989@gmail.com> Hi, Thanks Greg and Jeremy for your input. @Greg: I don?t have a strong preference whether the information should live on the wiki or on the Docs webpage, if we make it visible. The processes to report a vulnerability as well as to process and address it, is quite static. In that sense, I think it would make sense to consider adding it to the rest of the project?s documentation, if there is a logical place to put it. I think that we have most of the information in the different documents already, it is more the question of organizing and making it more visible. Currently it is much easier to find information about security related features that users care about. When it comes to vulnerabilities that most likely people who operate the platform will find, we need to make it easier for them to figure out how to deal with those issues, ie reporting them without doing any harm. I like Jeremy?s suggestions with regards to utilizing the website and documentation page to give visibility to the process. What do others think? Thanks, Ildik? > On Jul 13, 2023, at 04:55, Jeremy Stanley wrote: > > On 2023-07-13 11:30:43 +0000 (+0000), Waines, Greg wrote: > [...] >> Wrt to making this info (i.e. https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ) more visible. >> Currently it requires you to navigate as follows: >> - StarlingX WIKI https://wiki.openstack.org/wiki/StarlingX >> - StarlingX sub-projects > Security project https://wiki.openstack.org/wiki/StarlingX/Security >> - Select 'Vulnerability Management Process' https://wiki.openstack.org/wiki/StarlingX/Security#Vulnerability_Management_Process >> - Select ' See https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ' >> >> We could put an additional direct link to it higher in the WIKI >> - maybe under 'Planning & Processes' > [...] > > I'm not sure your Vulnerability Management Process document is what > needs increased visibility. Stepping back a bit, if I'm a StarlingX > user who isn't well-connected with the contributor community and I > find a misbehavior in the platform that I think might have security > implications, I'll likely want to know how to safely report that to > the StarlingX maintainers. > > I'm going to go to https://starlingx.io/ and start looking for > information on how to report security issues. I'll keyword search > for "security" on the main page of that project site and find that > it appears twice, but associated with a link to a video about tamper > resistance features, so that's not it. I'll maybe try searching for > "vu..." nope nothing. Okay maybe it's on the FAQs page? No, not > there either. In the docs? Oh hey look, there's a security section. > Never mind, it's about more security features of the platform. > > I might eventually stumble on that kinda subtle link to the > StarlingX wiki from the main documentation page and find the link > there to the Security sub-project and then the > https://wiki.openstack.org/wiki/StarlingX/Security#How_to_report_security_issues_to_StarlingX > section therein, but it's also quite possible I will have given up > before getting that far, or asked on a mailing list and naively > disclosed some details of a vulnerability when doing so. > > My suggestion is to get a link to that Security sub-team page in the > footers of everything on the starlingx.io and docs.starlingx.io > sites. Keeping https://wiki.openstack.org/wiki/StarlingX/Security in > a wiki page is fine if you don't think it's suitable to move into > your docs repository (or to have a separate repository the Security > sub-team can use for their publications), but I also recommend > moving the bug reporting instructions farther up that page. Ideally > it would be about the first thing someone sees when landing there > (perhaps after a brief intro paragraph). > -- > Jeremy Stanley > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From mason at ftlcomputing.com Fri Jul 14 17:30:45 2023 From: mason at ftlcomputing.com (Mason Schmitt) Date: Fri, 14 Jul 2023 10:30:45 -0700 Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility In-Reply-To: <1FAE18CB-B495-4E73-8D22-021ACCC7C989@gmail.com> References: <617AF541-97DB-455A-A267-DA472F2B1B0B@openinfra.dev> <20230713115505.gepaob2fhbroxrk3@yuggoth.org> <1FAE18CB-B495-4E73-8D22-021ACCC7C989@gmail.com> Message-ID: I think Jeremy's suggestion of a central security page, with links in the footer of most StarlingX content is an excellent idea. I completely agree that looking at this from the perspective of people that aren't yet well connected to the community is the right way to approach the question, for all of the reasons Jeremy gave. -- Mason On Thu, Jul 13, 2023 at 8:45?AM Ildiko Vancsa wrote: > Hi, > > Thanks Greg and Jeremy for your input. > > @Greg: I don?t have a strong preference whether the information should > live on the wiki or on the Docs webpage, if we make it visible. The > processes to report a vulnerability as well as to process and address it, > is quite static. In that sense, I think it would make sense to consider > adding it to the rest of the project?s documentation, if there is a logical > place to put it. > > I think that we have most of the information in the different documents > already, it is more the question of organizing and making it more visible. > Currently it is much easier to find information about security related > features that users care about. When it comes to vulnerabilities that most > likely people who operate the platform will find, we need to make it easier > for them to figure out how to deal with those issues, ie reporting them > without doing any harm. > > I like Jeremy?s suggestions with regards to utilizing the website and > documentation page to give visibility to the process. > > What do others think? > > Thanks, > Ildik? > > > > On Jul 13, 2023, at 04:55, Jeremy Stanley wrote: > > > > On 2023-07-13 11:30:43 +0000 (+0000), Waines, Greg wrote: > > [...] > >> Wrt to making this info (i.e. > https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management > ) more visible. > >> Currently it requires you to navigate as follows: > >> - StarlingX WIKI https://wiki.openstack.org/wiki/StarlingX > >> - StarlingX sub-projects > Security project > https://wiki.openstack.org/wiki/StarlingX/Security > >> - Select 'Vulnerability Management Process' > https://wiki.openstack.org/wiki/StarlingX/Security#Vulnerability_Management_Process > >> - Select ' See > https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management > ' > >> > >> We could put an additional direct link to it higher in the WIKI > >> - maybe under 'Planning & Processes' > > [...] > > > > I'm not sure your Vulnerability Management Process document is what > > needs increased visibility. Stepping back a bit, if I'm a StarlingX > > user who isn't well-connected with the contributor community and I > > find a misbehavior in the platform that I think might have security > > implications, I'll likely want to know how to safely report that to > > the StarlingX maintainers. > > > > I'm going to go to https://starlingx.io/ and start looking for > > information on how to report security issues. I'll keyword search > > for "security" on the main page of that project site and find that > > it appears twice, but associated with a link to a video about tamper > > resistance features, so that's not it. I'll maybe try searching for > > "vu..." nope nothing. Okay maybe it's on the FAQs page? No, not > > there either. In the docs? Oh hey look, there's a security section. > > Never mind, it's about more security features of the platform. > > > > I might eventually stumble on that kinda subtle link to the > > StarlingX wiki from the main documentation page and find the link > > there to the Security sub-project and then the > > > https://wiki.openstack.org/wiki/StarlingX/Security#How_to_report_security_issues_to_StarlingX > > section therein, but it's also quite possible I will have given up > > before getting that far, or asked on a mailing list and naively > > disclosed some details of a vulnerability when doing so. > > > > My suggestion is to get a link to that Security sub-team page in the > > footers of everything on the starlingx.io and docs.starlingx.io > > sites. Keeping https://wiki.openstack.org/wiki/StarlingX/Security in > > a wiki page is fine if you don't think it's suitable to move into > > your docs repository (or to have a separate repository the Security > > sub-team can use for their publications), but I also recommend > > moving the bug reporting instructions farther up that page. Ideally > > it would be about the first thing someone sees when landing there > > (perhaps after a brief intro paragraph). > > -- > > Jeremy Stanley > > _______________________________________________ > > Starlingx-discuss mailing list > > Starlingx-discuss at lists.starlingx.io > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Steve.Geary at windriver.com Fri Jul 14 18:07:05 2023 From: Steve.Geary at windriver.com (Geary, Stephen (Steve)) Date: Fri, 14 Jul 2023 18:07:05 +0000 Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility In-Reply-To: References: Message-ID: I read the issue as more than visibility. I see an opportunity, if not need, to adopt best practices and industry standard practices associated with vulnerability reporting and management. Maybe we could look to OpenSSF for ideas and first steps: https://github.com/ossf/wg-vulnerability-disclosures/blob/main/README.md -steve -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Wednesday, July 12, 2023 6:30 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 62, Issue 22 CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Vulnerability Management guidelines - improving visibility (Ildiko Vancsa) 2. Re: Vulnerability Management guidelines - improving visibility (Waines, Greg) ---------------------------------------------------------------------- Message: 1 Date: Tue, 11 Jul 2023 13:51:02 -0700 From: Ildiko Vancsa To: StarlingX ML Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility Message-ID: Content-Type: text/plain; charset=utf-8 Hi StarlingX Community, The StarlingX project has been gaining new users and contributors lately, and the community already started to look into providing more on-boarding related materials and help people to find their ways around. Related to the above, I wanted to bring up the project?s Vulnerability Management guidelines. While there is some documentation available on the StarlingX wiki[1] currently, it is not the easiest to find. As this is a crucial area, I think it would be a good time to both make sure that the information there is up to date, as well as to make the documentation easier to find. Would it make sense to move the content of the aforementioned wiki over to the Documentation website? Regardless of where the information lives, where do you think would be good to add pointers to it, ie. the project?s homepage, the docs homepage, etc? Best Regards, Ildik? [1] https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation ------------------------------ Message: 2 Date: Wed, 12 Jul 2023 11:49:20 +0000 From: "Waines, Greg" To: Ildiko Vancsa , StarlingX ML Subject: Re: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility Message-ID: Content-Type: text/plain; charset="utf-8" We do have a high level view of 'CVE Maintenance' in docs.starlingx.io . https://docs.starlingx.io/security/kubernetes/cve-maintenance-723cd9dd54b3.html We could provide a reference/link here to the more detailed page in the wiki . Greg. -----Original Message----- From: Ildiko Vancsa Sent: Tuesday, July 11, 2023 4:51 PM To: StarlingX ML Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, The StarlingX project has been gaining new users and contributors lately, and the community already started to look into providing more on-boarding related materials and help people to find their ways around. Related to the above, I wanted to bring up the project?s Vulnerability Management guidelines. While there is some documentation available on the StarlingX wiki[1] currently, it is not the easiest to find. As this is a crucial area, I think it would be a good time to both make sure that the information there is up to date, as well as to make the documentation easier to find. Would it make sense to move the content of the aforementioned wiki over to the Documentation website? Regardless of where the information lives, where do you think would be good to add pointers to it, ie. the project?s homepage, the docs homepage, etc? Best Regards, Ildik? [1] https://wiki.openstack.org/wiki/StarlingX/Security/Vulnerability_Management ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io ------------------------------ End of Starlingx-discuss Digest, Vol 62, Issue 22 ************************************************* From fungi at yuggoth.org Fri Jul 14 18:58:45 2023 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 14 Jul 2023 18:58:45 +0000 Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility In-Reply-To: References: Message-ID: <20230714185844.jyb2gj76yfoyp366@yuggoth.org> On 2023-07-14 18:07:05 +0000 (+0000), Geary, Stephen (Steve) wrote: > I read the issue as more than visibility. I see an opportunity, if > not need, to adopt best practices and industry standard practices > associated with vulnerability reporting and management. Maybe we > could look to OpenSSF for ideas and first steps: > https://github.com/ossf/wg-vulnerability-disclosures/blob/main/README.md [...] For what it's worth, the OpenStack Vulnerability Management Process (on which StarlingX's is based) was a major source of inspiration for the eventual OpenSSF guidelines and can be found referenced in the bibliography section here: https://github.com/ossf/oss-vulnerability-guide/blob/main/finder-guide.md#bibliography As well as the acknowledgements here: https://github.com/ossf/oss-vulnerability-guide/blob/main/maintainer-guide.md#acknowledgements More input is always useful, which is why we got involved in the drafting of those guidelines to begin with. (Full disclosure for those who don't know me: I'm the longest serving member of the OpenStack VMT and was consulted on the original OpenSSF guidelines, so do have some history with it.) What are your concerns with the current processes being followed, and what sorts of ideas specifically are you looking for? -- 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 Steve.Geary at windriver.com Mon Jul 17 21:08:18 2023 From: Steve.Geary at windriver.com (Geary, Stephen (Steve)) Date: Mon, 17 Jul 2023 21:08:18 +0000 Subject: [Starlingx-discuss] Vulnerability Management guidelines - improving visibility Message-ID: Jeremy, First, thank you for your contributions! Your contribution history actually addressed the uneasiness I was developing based upon my read of the thread. Comments and phrases in the thread led me to believe (incorrectly) we may trying to create something that industry and community processes and best practices have solved. All good and thanks! -steve -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Tue Jul 18 14:10:42 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 18 Jul 2023 14:10:42 +0000 Subject: [Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230714T060000Z Message-ID: Sanity Test from 2023 July 17 (https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230714T060000Z/outputs/iso/starlingx-intel-x86-64-cd.iso) Status: GREEN SX sanity Passed: 17 (100.0%) Failed: 0 (0.0%) Total Executed: 17 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_2p_2_big_pod_best_effort_HT_AIO PASS test_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_mixed_add_vf_interface[1] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] DX sanity Passed: 19 (100.0%) Failed: 0 (0.0%) Total Executed: 19 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_swact_controller_platform PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_push_docker_image_to_local_registry_standby PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] PASS test_bmc_verify_bm_type_ipmi PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Lucas.DeAtaidesBarreto at windriver.com Tue Jul 18 18:03:46 2023 From: Lucas.DeAtaidesBarreto at windriver.com (De Ataides Barreto, Lucas) Date: Tue, 18 Jul 2023 18:03:46 +0000 Subject: [Starlingx-discuss] Sanity and Regression - StarlingX + STX-Openstack MASTER build [20230714T060000Z] results - Jul - 18 Message-ID: Hi all, StarlingX + STX-Openstack sanity and regression results: Overall Status: RED Build Info: Build date: July 14 - 20230714T060000Z ISO: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230714T060000Z/outputs/iso/starlingx-intel-x86-64-20230714173515-cd.iso Helm Chart: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230714T060000Z/outputs/helm-charts/stx-openstack-1.0-1.stx.56-debian-stable-versioned.tgz The STX-Openstack application failed to apply due to the #2028061 launchpad: STX-Openstack apply failed on the openvswitch helm release (https://bugs.launchpad.net/starlingx/+bug/2028061). The team is already working on a fix for it and should be good for the next sanity run. Thanks, STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From ThalesElero.Cervi at windriver.com Tue Jul 18 18:14:15 2023 From: ThalesElero.Cervi at windriver.com (Cervi, Thales Elero) Date: Tue, 18 Jul 2023 18:14:15 +0000 Subject: [Starlingx-discuss] Minutes: OpenStack Distro Team Call (Jul 18, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-distro-openstack-meetings Minutes from the OpenStack Distro team call Jul 18, 2023 Build: - Build Issues: None Installation: - Installation Issues: # LP 2028061: STX-Openstack apply failed on the openvswitch helm release - Found today (July 18th). Fix proposed: https://review.opendev.org/c/starlingx/integ/+/888781 Sanity with stx-openstack (main branch): - Last Successful Execution: (OVS) Tue Jul 11 12:39:12 UTC 2023 - Overall status: GREEN ??????Sanity - Passed: 15 (100.00%) | Failed: 0 (0.0%) ??????Regression - Passed: 12 (100.00%) | Failed: 0 (0.0%) - Last Execution: (OVS) Tue Jul 18 12:39:12 UTC 2023 - Overall status: RED (# LP 2028061) ??????Sanity - Executed: 0 (0.0%) ??????Regression - Executed: 0 (0.0%) - Bugs Affecting Weekly Sanity/Regression: - No Reproducible bugs currently open. Only intermittent issues # LP 2023657: STX-O| config-out-of-date alarm won't disappear on controller-1 after swact and reapplying app # LP 2012389: STX-Openstack: Failed to activate binding for port for live migration # LP 2007303: STX-Openstack: "nova live-migration" fails to live migrate after host is forcefully turned off/on - StarlingX 9.0 Release: - Storyboard/Tasks for containerizing OpenStack clients: https://storyboard.openstack.org/#!/story/2010774 - Majority of the development is done (still using Ussuri based clients inside the container) - Documentation updates will be required: Task 48413 - Follow-up/Improvement tasks: Tasks 48410 and 48411 - Storyboard/Tasks for OpenStack upversion (Antelope): https://storyboard.openstack.org/#!/story/2010715 - In progress - We need the platform/application manifest decoupling to finish this work - Locally building the packages we faced an issue with required build dependencies that are higher than our current debian-bullseye.lst entries (e.g. oslo-db, sqlalchemy, keystone-auth) - Locally building the docker images: faced similar issue with required build dependencies (pip versioning conflicts and upper-constraints mismatches) - Storyboard/Tasks for decoupling platform and application manifests: https://storyboard.openstack.org/#!/story/2010797 - Infra team is prioritizing the CENGN decommission and will act on it after that -- Best Regards, Thales Elero Cervi -------------- next part -------------- An HTML attachment was scrubbed... URL: From Rob.Cooke at windriver.com Tue Jul 18 19:38:29 2023 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Tue, 18 Jul 2023 19:38:29 +0000 Subject: [Starlingx-discuss] Minutes: Test Status Call - July 18, 2023 Message-ID: Hi everyone, Please find below the minutes from this week's StarlingX Test Status Call: Minutes for 07/18/2023 * Open Topics: ? Plan to discuss the feature list for STX9.0 in the release call this week. * Is there a plan to revisit the list, are all items still planned for STX9.0, does the list need refinement etc. * Sanity Status: o Sanity on STX 9.0 - Green ? Last execution, July 17, 2023 - Results email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014295.html o Sanity on STX 9.0 plus Openstack - Red ? Last execution, July 17, 2023 - Results email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014296.html ? The STX-Openstack application failed to apply due to the #2028061 launchpad: STX-Openstack apply failed on the openvswitch helm release (https://bugs.launchpad.net/starlingx/+bug/2028061). The team is already working on a fix for it and should be good for the next sanity run. * Feature Test Status: o Feature testing is tracked in the following google sheet: ? https://docs.google.com/spreadsheets/d/1El3g0ute5K2S5DTR9p_rxa1jQlq8gcUzgMCNCE_sx8g/edit#gid=968103774 ? Some features are in progress, sheet does need updating ACTION: Rob/Nimalini * Regression Testing will be tracked here closer to release end: ? https://docs.google.com/spreadsheets/d/1NjYk9N0whK91nHViB5HFG2C1-XdJ09StVuLMxsz0KAY/edit?pli=1#gid=1717644237 Thanks, Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: From Charles.Short at windriver.com Tue Jul 18 20:07:59 2023 From: Charles.Short at windriver.com (Short, Charles) Date: Tue, 18 Jul 2023 20:07:59 +0000 Subject: [Starlingx-discuss] Apt-ostree repository Message-ID: Hi, I been working on a Debian based ostree package management system for the past couple of months. It is similar to how rpm-ostree manages packages with ostree on Fedora. I was wondering if there were any objections to adding the repository to the starlingx namespace on opendev.org? Thanks chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openstack.org Wed Jul 19 05:19:04 2023 From: ildiko at openstack.org (Ildiko Vancsa) Date: Tue, 18 Jul 2023 22:19:04 -0700 Subject: [Starlingx-discuss] Contributor recognition and appreciation Message-ID: Hi StarlingX Community, I would like to share an idea that came up during the StarlingX Marketing team call today. The team was talking about thoughts for the ongoing celebration of the project?s 5th year anniversary, and the idea of contributor recognition and appreciation came up. As the community has changed significantly since its inception, we thought to rather implement this per release and do it at the end of each cycle. The goal is to recognize the contributors at each release cycle who go above and beyond for the project and community. While everybody?s work and contributions are invaluable, not all of those are equally visible, which this idea is targeted to address. We didn?t discuss the process in deep details, but a few things that came up included: * Have a nomination process towards the end of the release cycles, where contributors can nominate people * We can hold a ceremony during a Community Call when a new release comes out * We can write a blog post to highlight contributors and their work - OpenStack Contributor Award blog post as an example: https://superuser.openinfra.dev/articles/openstack-community-contributor-awards-recognize-unsung-heroes-sydney/ What do you all think? Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation From Ghada.Khalil at windriver.com Wed Jul 19 12:30:14 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 19 Jul 2023 12:30:14 +0000 Subject: [Starlingx-discuss] No release meeting today July 19 Message-ID: Hello all, I will not be able to chair the StarlingX release meeting at 9:30 ET today (Jul 19) as I am out of office. I was not able to arrange a delegate. Therefore, I will cancel the meeting. Sorry for the inconvenience and the short notice. Regards, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Wed Jul 19 12:30:33 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Wed, 19 Jul 2023 12:30:33 +0000 Subject: [Starlingx-discuss] Canceled: Bi-weekly StarlingX Release Meeting Message-ID: Updated meeting series for the StarlingX Release Meeting Starting from Nov 9, 2022 and meeting every other week. Bi-weekly meeting on Wednesday 06:30AM PT / 09:30AM ET / 02:30PM UTC Zoom Link: https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 Meeting agenda/minutes: https://etherpad.openstack.org/p/stx-releases Regards, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 1942 bytes Desc: not available URL: From starlingx.build at gmail.com Wed Jul 19 13:52:04 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 19 Jul 2023 09:52:04 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_debian_master - Build # 224 - Failure! Message-ID: <883619282.72.1689774727286.JavaMail.javamailuser@localhost> Project: STX_build_debian_master Build #: 224 Status: Failure Timestamp: 20230716T174940Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230716T174940Z/logs -------------------------------------------------------------------------------- Parameters BUILD_PACKAGES_LIST: CLEAN_DOWNLOADS: false BUILD_HELM_CHARTS: true USE_DOCKER_CACHE: true DOCKER_IMAGE_LIST: PUSH_DOCKER_IMAGES: true CLEAN_DOCKER: true REFRESH_SOURCE: true DRY_RUN: false CLEAN_PACKAGES: true BUILD_RT: true BUILD_PACKAGES: true CLEAN_REPOMGR: true PKG_REUSE: false JENKINS_SCRIPTS_BRANCH: master BUILD_DOCKER_BASE_IMAGE: true BUILD_DOCKER_IMAGES: true FORCE_BUILD: false REBUILD_BUILDER_IMAGES: true CLEAN_ISO: true BUILD_ISO: true From starlingx.build at gmail.com Wed Jul 19 13:53:02 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 19 Jul 2023 09:53:02 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] STX_8.0_build_debian - Build # 34 - Failure! Message-ID: <1194819967.75.1689774784622.JavaMail.javamailuser@localhost> Project: STX_8.0_build_debian Build #: 34 Status: Failure Timestamp: 20230715T060000Z Branch: Check logs at: $PUBLISH_LOGS_URL -------------------------------------------------------------------------------- Parameters BUILD_PACKAGES_LIST: CLEAN_DOWNLOADS: false BUILD_HELM_CHARTS: true USE_DOCKER_CACHE: true DOCKER_IMAGE_LIST: PUSH_DOCKER_IMAGES: true CLEAN_DOCKER: true REFRESH_SOURCE: true DRY_RUN: false CLEAN_PACKAGES: true BUILD_RT: true BUILD_PACKAGES: true CLEAN_REPOMGR: true PKG_REUSE: false JENKINS_SCRIPTS_BRANCH: r/stx.8.0 BUILD_DOCKER_BASE_IMAGE: true BUILD_DOCKER_IMAGES: true FORCE_BUILD: false REBUILD_BUILDER_IMAGES: true CLEAN_ISO: true BUILD_ISO: true From ElisamaraAoki.Goncalves at windriver.com Wed Jul 19 14:00:49 2023 From: ElisamaraAoki.Goncalves at windriver.com (Goncalves, Elisamara Aoki) Date: Wed, 19 Jul 2023 14:00:49 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 13-07-2023 Message-ID: Hello All, Here are this week?s doc team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Thursdays 6:00 a.m. PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Elisamara Aoki Gon?alves ======= 13 July-23 Current StarlingX Release Stx 9.0 Release Tracking Spreadsheet: Doc Stories are tracked in https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing. Gerrit Reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - To be reviewed and merged - 5 reviews - Bruno Muniz / Gustavo Herzmann created a gerrit review to use the automated script for Vbox installs: To raise LP Bugs / Stories; https://storyboard.openstack.org/#!/story/2005051#comment-203593; Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 7 outstanding bugs - (4 were fixed) The DOC team to create LP defects corresponding with any DS defects - WIP. Teams to add all the impacted Releases when raising a LP bug - Bug #1932314 ?Virtual AIO-SX install documentation presents data...? : Bugs : StarlingX (launchpad.net) - To discuss with Greg Miscellaneous Updates: - We have a fault that is preventing LPs from closing when the coorsponding Gerrit WFs. Ron spoke with Jeremy Stanley, who reproduced the bug and is investigating. - Ron to update the Verified H/W page with the automated script updates https://www.windriver.com/studio/operator/self-validated-and-certified-hosts# - Currently Commented out - Script needs to be updated- Waiting for updates to the script -AR Ron - Bruno Muniz showed interest in creating DOC Videos supporting the StarlingX Installation Process. To check with Ildiko / Greg whether this is ok. These Videos can be hosted in a location in StarlingX. The Installation Docs can point to these videos - AR Bruno to get approvals from Ildiko / Greg - Sphinx Tools - Need to have further discussions about the version used upstream vs. downstream - AR Ron -To determine version. - Docker Container upstream / downstream - AR Ron (Discuss it with Greg / Ildiko) - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) - OpenInfra Summit & PTG Recording: https://ptg.opendev.org/etherpads.html - Workshop Details are tracked in https://etherpad.opendev.org/p/stx_hands_on_workshop_2023 - IRC: Everyone to use the IRC channel for communication with the community. Team can use https://www.icechat.net/site/icechat-9/ as an alternate text editor from their browser. IRC is a chat platform, for text-based communication. There?s a web client for easy access: https://webchat.oftc.net/- You need to pick a nickname, and the channel name is #opendev. Once you are in the #opendev channel, you can talk to the group of people in that channel. To Setup IRC ? contributor-guide documentation (openstack.org) IRC here: https://docs.openstack.org/contributors/common/irc.html; Engineering Status: StarlingX Eng Stx Status: https://etherpad.opendev.org/p/stx-status StarlingX Eng Status 2023 https://etherpad.opendev.org/p/stx-cores ____________________________ 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 Wed Jul 19 13:24:54 2023 From: Scott.Little at windriver.com (Little, Scott) Date: Wed, 19 Jul 2023 13:24:54 +0000 Subject: [Starlingx-discuss] Transition away from CENGN Message-ID: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> As you should all be aware by now, StarlingX will be relocating our build and mirror service away from CENGN.? The replacement host, at least for the near future, will be Wind River.? CENGN has graciously offered to redirect traffic referencing mirror.starlingx.cengn.ca to our new home at mirror.starlingx.windriver.com for an extended period to ease the transition. The Wind River infrastructure is now ready.? We need to plan a time for the transition.? During the transition, we'll need to disable builds for a day or two.? This will give us a bit of time to ensure the Wind River is fully up to date with the final CENGN content.? We will discuss the timing at this weeks community meeting.? If you have concerns, please attend. Scott Little From ElisamaraAoki.Goncalves at windriver.com Wed Jul 19 14:04:20 2023 From: ElisamaraAoki.Goncalves at windriver.com (Goncalves, Elisamara Aoki) Date: Wed, 19 Jul 2023 14:04:20 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 06-07-2023 Message-ID: Hello All, Here are this week?s doc team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Thursdays 6:00 a.m. PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Elisamara Aoki Gon?alves ======= 06 July-23 Note: From July 1st week the StarlingX DOC meetings will be switching over to Thursday 6.00 a.m. PST. See https://wiki.openstack.org/wiki/Starlingx/Meetings for more details. Password to be set by the first joinee at the meeting. Note: We will be cancelling the Wednesday StarlingX Doc Team Meetings from July 1st. Current StarlingX Release Stx 9.0 Release Tracking Spreadsheet: Doc Stories are tracked in https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing. Gerrit Reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - To be reviewed and merged - 5 reviews - Bruno Muniz / Gustavo Herzmann created a gerrit review to use the automated script for Vbox installs: To raise LP Bugs / Stories; https://storyboard.openstack.org/#!/story/2005051#comment-203593; Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 7 outstanding bugs - (4 were fixed) The DOC team to create LP defects corresponding with any DS defects - WIP. Teams to add all the impacted Releases when raising a LP bug - To update Ildiko about LP bugs not closing automatically when Gerrit reviews merge. - AR Juanita - Bug #2021896 ?References to not supported Rook container-based C...? : Bugs : StarlingX (launchpad.net) - closed - Bug #1932314 ?Virtual AIO-SX install documentation presents data...? : Bugs : StarlingX (launchpad.net) - To discuss with Greg Miscellaneous Updates: - Ron to update the Verified H/W page with the automated script updates https://www.windriver.com/studio/operator/self-validated-and-certified-hosts# - Currently Commented out - Script needs to be updated- Waiting for updates to the script -AR Ron - Installation Virtual docs - Bruno to ask Greg at the community meeting or send an email General Updates: - As far as discussions go the OpenDev team meets regularly in #opendev-meeting (on the OFTC IRC network) on Tuesdays at 19:00 UTC. We also have the #opendev IRC channel and service-discuss at lists.opendev.org mailing list. Similarly Zuul has the https://matrix.to/#/#zuul:opendev.org Matrix room and zuul-discuss at lists.zuul-ci.org mailing list. - Bruno Muniz showed interest in creating DOC Videos supporting the StarlingX Installation Process. To check with Ildiko / Greg whether this is ok. These Videos can be hosted in a location in StarlingX. The Installation Docs can point to these videos - AR Bruno to get approvals from Ildiko / Greg - Sphinx Tools - Need to have further discussions about the version used upstream vs. downstream - AR Ron -To determine version. - Docker Container upstream / downstream - AR Ron (Discuss it with Greg / Ildiko) - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) - OpenInfra Summit & PTG Recording: https://ptg.opendev.org/etherpads.html - Workshop Details are tracked in https://etherpad.opendev.org/p/stx_hands_on_workshop_2023 - IRC: Everyone to use the IRC channel for communication with the community. Team can use https://www.icechat.net/site/icechat-9/ as an alternate text editor from their browser. IRC is a chat platform, for text-based communication. There?s a web client for easy access: https://webchat.oftc.net/- You need to pick a nickname, and the channel name is #opendev. Once you are in the #opendev channel, you can talk to the group of people in that channel. To Setup IRC ? contributor-guide documentation (openstack.org) IRC here: https://docs.openstack.org/contributors/common/irc.html; Engineering Status: StarlingX Eng Stx Status: https://etherpad.opendev.org/p/stx-status StarlingX Eng Status 2023 https://etherpad.opendev.org/p/stx-cores 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 Wed Jul 19 14:16:43 2023 From: starlingx.build at gmail.com (starlingx.build at gmail.com) Date: Wed, 19 Jul 2023 10:16:43 -0400 (EDT) Subject: [Starlingx-discuss] [build-report] master STX_build_debian_master - Build # 225 - Still Failing! In-Reply-To: <29278717.70.1689774723695.JavaMail.javamailuser@localhost> References: <29278717.70.1689774723695.JavaMail.javamailuser@localhost> Message-ID: <892751090.78.1689776204661.JavaMail.javamailuser@localhost> Project: STX_build_debian_master Build #: 225 Status: Still Failing Timestamp: 20230719T135207Z Branch: master Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230719T135207Z/logs -------------------------------------------------------------------------------- Parameters BUILD_PACKAGES_LIST: CLEAN_DOWNLOADS: false BUILD_HELM_CHARTS: true USE_DOCKER_CACHE: true DOCKER_IMAGE_LIST: PUSH_DOCKER_IMAGES: true CLEAN_DOCKER: true REFRESH_SOURCE: true DRY_RUN: false CLEAN_PACKAGES: true BUILD_RT: true BUILD_PACKAGES: true CLEAN_REPOMGR: true PKG_REUSE: false JENKINS_SCRIPTS_BRANCH: master BUILD_DOCKER_BASE_IMAGE: true BUILD_DOCKER_IMAGES: true FORCE_BUILD: false REBUILD_BUILDER_IMAGES: true CLEAN_ISO: true BUILD_ISO: true From Scott.Little at windriver.com Wed Jul 19 14:44:37 2023 From: Scott.Little at windriver.com (Little, Scott) Date: Wed, 19 Jul 2023 14:44:37 +0000 Subject: [Starlingx-discuss] Transition away from CENGN In-Reply-To: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> References: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> Message-ID: Based on the community call, the agreed plan is as follows. - Allow the current CENGN master branch build to complete. - Freeze further build attempts on CENGN as of July 20? 04:00 UTC. - Final sync of the Wind River mirror relative to the CENGN mirror starts Jul 20 13:00 UTC - DNS changed to redirect mirror.starlingx.cengn.ca to mirror.starlingx.windriver.com Jul 20 16:00 UTC - Test build(s) of StarlingX in Wind River hardware Jul 20 16:00 UTC- July 21 20:00 UTC - July 21 20:00 UTC... If tests are successful, start scheduled builds on Wind River infrastructure, otherwise revert to CENGN as re-enable scheduled builds on their side. If there are objections to this plan, please speak out today. Scott On 2023-07-19 09:24, Little, Scott wrote: > As you should all be aware by now, StarlingX will be relocating our > build and mirror service away from CENGN.? The replacement host, at > least for the near future, will be Wind River.? CENGN has graciously > offered to redirect traffic referencing mirror.starlingx.cengn.ca to our > new home at mirror.starlingx.windriver.com for an extended period to > ease the transition. > > The Wind River infrastructure is now ready.? We need to plan a time for > the transition.? During the transition, we'll need to disable builds for > a day or two.? This will give us a bit of time to ensure the Wind River > is fully up to date with the final CENGN content.? We will discuss the > timing at this weeks community meeting.? If you have concerns, please > attend. > > Scott Little > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From Greg.Waines at windriver.com Wed Jul 19 16:51:44 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Wed, 19 Jul 2023 16:51:44 +0000 Subject: [Starlingx-discuss] Apt-ostree repository In-Reply-To: References: Message-ID: Hey Chuck, I know we talked about this offline and it was also discussed in today's StarlingX Community meeting ... Just to clarify / add-some-detail to your request ... for community understanding ... * 'apt-ostree' is sort of a hybrid package manager that allows one to build and manage ostree commits based on DEB PKGs * You are developing this as part of the FLOCK project team's work on 'Software Upgrade/Update Evolution', see stx 9 feature plan spreadsheet https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit#gid=1107209846 . * * Your development plans for apt-ostree is to develop this generically (i.e. no starlingx specifics), using the debian apt package manager and debian's ostree package. * AND THEN the higher-level StarlingX-specific Software Management code would USE apt-ostree * * As discussed, our long term plans would be to offer/propose this as a debian package to the debian community .... Rather than bury this in starlingx. * And then we would just include this new debian package in our host packages and use it for starlingx * * In the meantime, you're proposing that we create an apt-ostree repo in starlingx, as sort of an incubation period ... in order to develop apt-ostree and meet stx 9 release schedules. * With the intent to move it to the debian community later. Greg. p.s. I'm a +1 for new short-term apt-ostree repo From: Short, Charles Sent: Tuesday, July 18, 2023 4:08 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Apt-ostree repository Hi, I been working on a Debian based ostree package management system for the past couple of months. It is similar to how rpm-ostree manages packages with ostree on Fedora. I was wondering if there were any objections to adding the repository to the starlingx namespace on opendev.org? Thanks chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: From Charles.Short at windriver.com Wed Jul 19 17:02:46 2023 From: Charles.Short at windriver.com (Short, Charles) Date: Wed, 19 Jul 2023 17:02:46 +0000 Subject: [Starlingx-discuss] Apt-ostree repository In-Reply-To: References: Message-ID: Hi Answers are in line. From: Waines, Greg Sent: Wednesday, July 19, 2023 12:52 PM To: Short, Charles ; starlingx-discuss at lists.starlingx.io Subject: RE: Apt-ostree repository Hey Chuck, I know we talked about this offline and it was also discussed in today's StarlingX Community meeting ... Just to clarify / add-some-detail to your request ... for community understanding ... * 'apt-ostree' is sort of a hybrid package manager that allows one to build and manage ostree commits based on DEB PKGs Correct it will become a hybrid image/package manager that allows to build and manage ostree commits based on Debian packages. * You are developing this as part of the FLOCK project team's work on 'Software Upgrade/Update Evolution', see stx 9 feature plan spreadsheet https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit#gid=1107209846 . Correct * * Your development plans for apt-ostree is to develop this generically (i.e. no starlingx specifics), using the debian apt package manager and debian's ostree package. That's correct I see possible use cases outside of StarlingX where it could possibly be used for example embedded systems for managing updates, installs, etc. * AND THEN the higher-level StarlingX-specific Software Management code would USE apt-ostree StarlingX manages large number of nodes well. I would hope that apt-ostree gets to the point where apt-ostree can manage Debian based systems well. * * As discussed, our long term plans would be to offer/propose this as a debian package to the debian community .... Rather than bury this in starlingx. * And then we would just include this new debian package in our host packages and use it for starlingx Correct I would like to start with small and then work our way through a bigger use case within the Debian community. * * In the meantime, you're proposing that we create an apt-ostree repo in starlingx, as sort of an incubation period ... in order to develop apt-ostree and meet stx 9 release schedules. * With the intent to move it to the debian community later. Correct Greg. p.s. I'm a +1 for new short-term apt-ostree repo From: Short, Charles > Sent: Tuesday, July 18, 2023 4:08 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Apt-ostree repository Hi, I been working on a Debian based ostree package management system for the past couple of months. It is similar to how rpm-ostree manages packages with ostree on Fedora. I was wondering if there were any objections to adding the repository to the starlingx namespace on opendev.org? Thanks chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openstack.org Wed Jul 19 21:45:20 2023 From: ildiko at openstack.org (Ildiko Vancsa) Date: Wed, 19 Jul 2023 14:45:20 -0700 Subject: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED In-Reply-To: <5f8269c6-c73e-b407-ab7d-ae5265e2cafc@windriver.com> References: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> <5f8269c6-c73e-b407-ab7d-ae5265e2cafc@windriver.com> Message-ID: Hi StarlingX Community, Thank you to everyone who already voted. For those who haven?t had the chance yet, it is a friendly reminder to please share your vote about moving to Matrix, to use it as the official chat tool for community communications. Please respond with ?+1?, if you are in support, or share your concerns, if there is any. Please hit ?reply all? to keep the mailing list in the thread with your response. I will share the results of the vote early next week, and propose next steps for the TSC to approve. Please let me know if you have any questions. Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 17, 2023, at 12:38, Chris Friesen wrote: > > +1, willing to give it a try. > > On 7/12/2023 5:14 PM, Ildiko Vancsa wrote: >> CAUTION: This email comes from a non Wind River email account! >> Do not click links or open attachments unless you recognize the sender and know the content is safe. >> >> Hi, >> >> Thank you all for the feedback so far! >> >> I haven?t received any objections against the option to start using Matrix as a chat tool for the StarlingX community. People had questions on the Community Call about the tool today, so I collected some useful information to help exploring it: >> >> - As a reminder, you can find out more about the tool here: https://matrix.org >> - There are different options to use as a browser or desktop client. Many of them are also available on smartphones. >> + I?m using Element - https://element.io >> + Some other options include >> ~ Weechat - https://github.com/poljar/weechat-matrix >> ~ SchildiChat - https://schildi.chat/ >> ~ FluffyChat - https://fluffychat.im/ >> >> - The #starlingX IRC channel is also available through Matrix - https://matrix.to/#/!XDOJNehPiaWKvYGWVD:matrix.org?via=matrix.org >> ~ You will need to create an account first >> ~ There is documentation available in the Zuul community?s docs about how to register - https://zuul-ci.org/docs/zuul/latest/howtos/matrix.html#create-an-account >> >> >> During the Community Call, it also came up that it would be great to agree on how we would like to utilize a chat tool. For instance, to aovid having too many channels, etc. The current proposal to the Matrix setup is the following: >> >> - Have multiple chat rooms available for community communication: >> + starlingx-general room - topics that are relevant to the whole community >> + StarlingX project team channels >> ~ topics that are relevant to a project team >> ~ ie: starlingx-build, starlingx-containers, etc >> + Optional channel ideas - specific topic areas that are outside of the existing project teams >> ~ starlingx-newcomers >> ~ starlingx-troubleshooting >> >> >> __ If you are in support to use Matrix as the chat tool for StarlingX moving forward, please reply to this email with ?+1?.__ >> >> >> Please let me know if you have any questions, or if you need help with setting up Matrix. >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Director of Community >> Open Infrastructure Foundation >> >> >> >> >> >>> On Jul 4, 2023, at 21:42, open infra wrote: >>> >>> CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord. >>> Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply). >>> >>> >>> >>> >>> >>> On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa wrote: >>> Hi StarlingX Community, >>> >>> I?m reaching out to you about a recurring topic that came up during the PTG last week again. >>> >>> While the community is actively using the mailing list, it is not always the best platform, as it doesn?t allow for more synchronous chat. Contributors at the event had a growing interest in finding a way to provide the opportunity for more synchronous communication to capture the project teams? chatters, and enable newcomers to reach out and start to participate. >>> >>> Challenges: >>> * Tooling: People raised that while it is an open protocol, IRC still doesn?t feel inclusive due to its simplicity. >>> * Format: The current one-channel setup doesn?t feel efficient and comfortable, since people need to address everyone in the channel with every topic they have a question or comment about. >>> >>> >>> Proposal to move forward: >>> * Tooling: The preferred tool in last week?s conversation was Matrix - https://matrix.org >>> - It is an open tool, which ensures continued access to the platform and its features >>> - It is more modern than IRC >>> >>> * Format: The idea came up to create multiple channels for the StarlingX project >>> - We can keep the all-community channel >>> - We can create channels for each project team, that are more topic specific >>> - We also have the option to create a channel for newcomers, which could include troubleshooting type of conversations as well >>> >>> >>> In order to identify next steps, please share your feedback about the proposal above. Ie: What do you think about Matrix? Would you be more comfortable using a chat tool with the more fine grained configuration of having multiple channels? >>> >>> Thanks and Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Director of Community >>> Open Infrastructure Foundation >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > From David.Liu at windriver.com Thu Jul 20 03:08:05 2023 From: David.Liu at windriver.com (Liu, David) Date: Thu, 20 Jul 2023 03:08:05 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 62, Issue 38 In-Reply-To: References: Message-ID: Hi, I'm working on submit some code for review, and the zuul gate job failed, but I can't download the detailed logs, is there a problem with The CI server side? My zuul job is here: https://zuul.opendev.org/t/openstack/build/760e0e486b024f9c9e5c5883af49299c/artifacts Thanks, David -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Thursday, July 20, 2023 1:03 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 62, Issue 38 CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Apt-ostree repository (Short, Charles) ---------------------------------------------------------------------- Message: 1 Date: Wed, 19 Jul 2023 17:02:46 +0000 From: "Short, Charles" To: "Waines, Greg" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Apt-ostree repository Message-ID: Content-Type: text/plain; charset="us-ascii" Hi Answers are in line. From: Waines, Greg Sent: Wednesday, July 19, 2023 12:52 PM To: Short, Charles ; starlingx-discuss at lists.starlingx.io Subject: RE: Apt-ostree repository Hey Chuck, I know we talked about this offline and it was also discussed in today's StarlingX Community meeting ... Just to clarify / add-some-detail to your request ... for community understanding ... * 'apt-ostree' is sort of a hybrid package manager that allows one to build and manage ostree commits based on DEB PKGs Correct it will become a hybrid image/package manager that allows to build and manage ostree commits based on Debian packages. * You are developing this as part of the FLOCK project team's work on 'Software Upgrade/Update Evolution', see stx 9 feature plan spreadsheet https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit#gid=1107209846 . Correct * * Your development plans for apt-ostree is to develop this generically (i.e. no starlingx specifics), using the debian apt package manager and debian's ostree package. That's correct I see possible use cases outside of StarlingX where it could possibly be used for example embedded systems for managing updates, installs, etc. * AND THEN the higher-level StarlingX-specific Software Management code would USE apt-ostree StarlingX manages large number of nodes well. I would hope that apt-ostree gets to the point where apt-ostree can manage Debian based systems well. * * As discussed, our long term plans would be to offer/propose this as a debian package to the debian community .... Rather than bury this in starlingx. * And then we would just include this new debian package in our host packages and use it for starlingx Correct I would like to start with small and then work our way through a bigger use case within the Debian community. * * In the meantime, you're proposing that we create an apt-ostree repo in starlingx, as sort of an incubation period ... in order to develop apt-ostree and meet stx 9 release schedules. * With the intent to move it to the debian community later. Correct Greg. p.s. I'm a +1 for new short-term apt-ostree repo From: Short, Charles > Sent: Tuesday, July 18, 2023 4:08 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Apt-ostree repository Hi, I been working on a Debian based ostree package management system for the past couple of months. It is similar to how rpm-ostree manages packages with ostree on Fedora. I was wondering if there were any objections to adding the repository to the starlingx namespace on opendev.org? Thanks chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io ------------------------------ End of Starlingx-discuss Digest, Vol 62, Issue 38 ************************************************* From Abhishek.Jaiswal at windriver.com Thu Jul 20 06:29:08 2023 From: Abhishek.Jaiswal at windriver.com (Jaiswal, Abhishek) Date: Thu, 20 Jul 2023 06:29:08 +0000 Subject: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED In-Reply-To: References: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> <5f8269c6-c73e-b407-ab7d-ae5265e2cafc@windriver.com> Message-ID: +1 Abhishek Jaiswal Member of Technical Staff M/?+91 7799126262 -----Original Message----- From: Ildiko Vancsa Sent: Thursday, July 20, 2023 3:15 AM To: StarlingX ML Subject: Re: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, Thank you to everyone who already voted. For those who haven?t had the chance yet, it is a friendly reminder to please share your vote about moving to Matrix, to use it as the official chat tool for community communications. Please respond with ?+1?, if you are in support, or share your concerns, if there is any. Please hit ?reply all? to keep the mailing list in the thread with your response. I will share the results of the vote early next week, and propose next steps for the TSC to approve. Please let me know if you have any questions. Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 17, 2023, at 12:38, Chris Friesen wrote: > > +1, willing to give it a try. > > On 7/12/2023 5:14 PM, Ildiko Vancsa wrote: >> CAUTION: This email comes from a non Wind River email account! >> Do not click links or open attachments unless you recognize the sender and know the content is safe. >> >> Hi, >> >> Thank you all for the feedback so far! >> >> I haven?t received any objections against the option to start using Matrix as a chat tool for the StarlingX community. People had questions on the Community Call about the tool today, so I collected some useful information to help exploring it: >> >> - As a reminder, you can find out more about the tool here: https://matrix.org >> - There are different options to use as a browser or desktop client. Many of them are also available on smartphones. >> + I?m using Element - https://element.io >> + Some other options include >> ~ Weechat - https://github.com/poljar/weechat-matrix >> ~ SchildiChat - https://schildi.chat/ >> ~ FluffyChat - https://fluffychat.im/ >> >> - The #starlingX IRC channel is also available through Matrix - https://matrix.to/#/!XDOJNehPiaWKvYGWVD:matrix.org?via=matrix.org >> ~ You will need to create an account first >> ~ There is documentation available in the Zuul community?s docs about how to register - https://zuul-ci.org/docs/zuul/latest/howtos/matrix.html#create-an-account >> >> >> During the Community Call, it also came up that it would be great to agree on how we would like to utilize a chat tool. For instance, to aovid having too many channels, etc. The current proposal to the Matrix setup is the following: >> >> - Have multiple chat rooms available for community communication: >> + starlingx-general room - topics that are relevant to the whole community >> + StarlingX project team channels >> ~ topics that are relevant to a project team >> ~ ie: starlingx-build, starlingx-containers, etc >> + Optional channel ideas - specific topic areas that are outside of the existing project teams >> ~ starlingx-newcomers >> ~ starlingx-troubleshooting >> >> >> __ If you are in support to use Matrix as the chat tool for StarlingX moving forward, please reply to this email with ?+1?.__ >> >> >> Please let me know if you have any questions, or if you need help with setting up Matrix. >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Director of Community >> Open Infrastructure Foundation >> >> >> >> >> >>> On Jul 4, 2023, at 21:42, open infra wrote: >>> >>> CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord. >>> Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply). >>> >>> >>> >>> >>> >>> On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa wrote: >>> Hi StarlingX Community, >>> >>> I?m reaching out to you about a recurring topic that came up during the PTG last week again. >>> >>> While the community is actively using the mailing list, it is not always the best platform, as it doesn?t allow for more synchronous chat. Contributors at the event had a growing interest in finding a way to provide the opportunity for more synchronous communication to capture the project teams? chatters, and enable newcomers to reach out and start to participate. >>> >>> Challenges: >>> * Tooling: People raised that while it is an open protocol, IRC still doesn?t feel inclusive due to its simplicity. >>> * Format: The current one-channel setup doesn?t feel efficient and comfortable, since people need to address everyone in the channel with every topic they have a question or comment about. >>> >>> >>> Proposal to move forward: >>> * Tooling: The preferred tool in last week?s conversation was Matrix - https://matrix.org >>> - It is an open tool, which ensures continued access to the platform and its features >>> - It is more modern than IRC >>> >>> * Format: The idea came up to create multiple channels for the StarlingX project >>> - We can keep the all-community channel >>> - We can create channels for each project team, that are more topic specific >>> - We also have the option to create a channel for newcomers, which could include troubleshooting type of conversations as well >>> >>> >>> In order to identify next steps, please share your feedback about the proposal above. Ie: What do you think about Matrix? Would you be more comfortable using a chat tool with the more fine grained configuration of having multiple channels? >>> >>> Thanks and Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Director of Community >>> Open Infrastructure Foundation >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io From Greg.Waines at windriver.com Thu Jul 20 11:11:33 2023 From: Greg.Waines at windriver.com (Waines, Greg) Date: Thu, 20 Jul 2023 11:11:33 +0000 Subject: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED In-Reply-To: References: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> <5f8269c6-c73e-b407-ab7d-ae5265e2cafc@windriver.com> Message-ID: +1 for matrix -----Original Message----- From: Ildiko Vancsa Sent: Wednesday, July 19, 2023 5:45 PM To: StarlingX ML Subject: Re: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, Thank you to everyone who already voted. For those who haven?t had the chance yet, it is a friendly reminder to please share your vote about moving to Matrix, to use it as the official chat tool for community communications. Please respond with ?+1?, if you are in support, or share your concerns, if there is any. Please hit ?reply all? to keep the mailing list in the thread with your response. I will share the results of the vote early next week, and propose next steps for the TSC to approve. Please let me know if you have any questions. Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 17, 2023, at 12:38, Chris Friesen wrote: > > +1, willing to give it a try. > > On 7/12/2023 5:14 PM, Ildiko Vancsa wrote: >> CAUTION: This email comes from a non Wind River email account! >> Do not click links or open attachments unless you recognize the sender and know the content is safe. >> >> Hi, >> >> Thank you all for the feedback so far! >> >> I haven?t received any objections against the option to start using Matrix as a chat tool for the StarlingX community. People had questions on the Community Call about the tool today, so I collected some useful information to help exploring it: >> >> - As a reminder, you can find out more about the tool here: https://matrix.org >> - There are different options to use as a browser or desktop client. Many of them are also available on smartphones. >> + I?m using Element - https://element.io >> + Some other options include >> ~ Weechat - https://github.com/poljar/weechat-matrix >> ~ SchildiChat - https://schildi.chat/ >> ~ FluffyChat - https://fluffychat.im/ >> >> - The #starlingX IRC channel is also available through Matrix - https://matrix.to/#/!XDOJNehPiaWKvYGWVD:matrix.org?via=matrix.org >> ~ You will need to create an account first >> ~ There is documentation available in the Zuul community?s docs about how to register - https://zuul-ci.org/docs/zuul/latest/howtos/matrix.html#create-an-account >> >> >> During the Community Call, it also came up that it would be great to agree on how we would like to utilize a chat tool. For instance, to aovid having too many channels, etc. The current proposal to the Matrix setup is the following: >> >> - Have multiple chat rooms available for community communication: >> + starlingx-general room - topics that are relevant to the whole community >> + StarlingX project team channels >> ~ topics that are relevant to a project team >> ~ ie: starlingx-build, starlingx-containers, etc >> + Optional channel ideas - specific topic areas that are outside of the existing project teams >> ~ starlingx-newcomers >> ~ starlingx-troubleshooting >> >> >> __ If you are in support to use Matrix as the chat tool for StarlingX moving forward, please reply to this email with ?+1?.__ >> >> >> Please let me know if you have any questions, or if you need help with setting up Matrix. >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Director of Community >> Open Infrastructure Foundation >> >> >> >> >> >>> On Jul 4, 2023, at 21:42, open infra wrote: >>> >>> CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord. >>> Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply). >>> >>> >>> >>> >>> >>> On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa wrote: >>> Hi StarlingX Community, >>> >>> I?m reaching out to you about a recurring topic that came up during the PTG last week again. >>> >>> While the community is actively using the mailing list, it is not always the best platform, as it doesn?t allow for more synchronous chat. Contributors at the event had a growing interest in finding a way to provide the opportunity for more synchronous communication to capture the project teams? chatters, and enable newcomers to reach out and start to participate. >>> >>> Challenges: >>> * Tooling: People raised that while it is an open protocol, IRC still doesn?t feel inclusive due to its simplicity. >>> * Format: The current one-channel setup doesn?t feel efficient and comfortable, since people need to address everyone in the channel with every topic they have a question or comment about. >>> >>> >>> Proposal to move forward: >>> * Tooling: The preferred tool in last week?s conversation was Matrix - https://matrix.org >>> - It is an open tool, which ensures continued access to the platform and its features >>> - It is more modern than IRC >>> >>> * Format: The idea came up to create multiple channels for the StarlingX project >>> - We can keep the all-community channel >>> - We can create channels for each project team, that are more topic specific >>> - We also have the option to create a channel for newcomers, which could include troubleshooting type of conversations as well >>> >>> >>> In order to identify next steps, please share your feedback about the proposal above. Ie: What do you think about Matrix? Would you be more comfortable using a chat tool with the more fine grained configuration of having multiple channels? >>> >>> Thanks and Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Director of Community >>> Open Infrastructure Foundation >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io From fungi at yuggoth.org Thu Jul 20 12:32:29 2023 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 20 Jul 2023 12:32:29 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 62, Issue 38 In-Reply-To: References: Message-ID: <20230720123228.fzrsixloayxl5hbf@yuggoth.org> On 2023-07-20 03:08:05 +0000 (+0000), Liu, David wrote: > I'm working on submit some code for review, and the zuul gate job > failed, but I can't download the detailed logs, is there a problem > with The CI server side? > > My zuul job is here: > https://zuul.opendev.org/t/openstack/build/760e0e486b024f9c9e5c5883af49299c/artifacts [...] I'm not sure what logs you think are missing, but the console log there shows that the pyflakes static analysis tool you're running encountered a fatal exception: AttributeError: 'FlakesChecker' object has no attribute 'JOINEDSTR' https://zuul.opendev.org/t/openstack/build/760e0e486b024f9c9e5c5883af49299c/log/job-output.txt#670 I'm able to reproduce this by checking out your change and running `tox -e pep8 -c distributedcloud-client/tox.ini` under python3.7, while running the same with a fresh checkout of the master branch completes successfully, so there's definitely something about https://review.opendev.org/888424 which is triggering the problem. A quick web search on the exact error string turns up this mailing list thread from 2019 about incompatibilities between the hacking plugin and (then) newer flake8/pyflakes versions: https://lists.openstack.org/pipermail/openstack-discuss/2019-November/011027.html My best guess, without digging deeper, is that something in the code being added in change 888424 is tickling the necessary code paths through pyflakes to hit the incompatibility with hacking. Indeed, editing distributedcloud-client/test-requirements.txt and bluntly replacing the hacking entry with just flake8 gets it to succeed, but of course this is only a reasonable solution if you don't care about the additional rules that module was enforcing. -- 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 ThalesElero.Cervi at windriver.com Thu Jul 20 13:20:11 2023 From: ThalesElero.Cervi at windriver.com (Cervi, Thales Elero) Date: Thu, 20 Jul 2023 13:20:11 +0000 Subject: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED In-Reply-To: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> References: <51533043-0776-4CEB-945B-C0CAF3E538E3@openinfra.dev> Message-ID: +1 for matrix ________________________________ From: Ildiko Vancsa Sent: Wednesday, July 12, 2023 8:14 PM To: StarlingX ML Subject: Re: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, Thank you all for the feedback so far! I haven?t received any objections against the option to start using Matrix as a chat tool for the StarlingX community. People had questions on the Community Call about the tool today, so I collected some useful information to help exploring it: - As a reminder, you can find out more about the tool here: https://matrix.org - There are different options to use as a browser or desktop client. Many of them are also available on smartphones. + I?m using Element - https://element.io + Some other options include ~ Weechat - https://github.com/poljar/weechat-matrix ~ SchildiChat - https://schildi.chat/ ~ FluffyChat - https://fluffychat.im/ - The #starlingX IRC channel is also available through Matrix - https://matrix.to/#/!XDOJNehPiaWKvYGWVD:matrix.org?via=matrix.org ~ You will need to create an account first ~ There is documentation available in the Zuul community?s docs about how to register - https://zuul-ci.org/docs/zuul/latest/howtos/matrix.html#create-an-account During the Community Call, it also came up that it would be great to agree on how we would like to utilize a chat tool. For instance, to aovid having too many channels, etc. The current proposal to the Matrix setup is the following: - Have multiple chat rooms available for community communication: + starlingx-general room - topics that are relevant to the whole community + StarlingX project team channels ~ topics that are relevant to a project team ~ ie: starlingx-build, starlingx-containers, etc + Optional channel ideas - specific topic areas that are outside of the existing project teams ~ starlingx-newcomers ~ starlingx-troubleshooting __ If you are in support to use Matrix as the chat tool for StarlingX moving forward, please reply to this email with ?+1?.__ Please let me know if you have any questions, or if you need help with setting up Matrix. Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 4, 2023, at 21:42, open infra wrote: > > CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord. > Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply). > > > > > > On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa wrote: > Hi StarlingX Community, > > I?m reaching out to you about a recurring topic that came up during the PTG last week again. > > While the community is actively using the mailing list, it is not always the best platform, as it doesn?t allow for more synchronous chat. Contributors at the event had a growing interest in finding a way to provide the opportunity for more synchronous communication to capture the project teams? chatters, and enable newcomers to reach out and start to participate. > > Challenges: > * Tooling: People raised that while it is an open protocol, IRC still doesn?t feel inclusive due to its simplicity. > * Format: The current one-channel setup doesn?t feel efficient and comfortable, since people need to address everyone in the channel with every topic they have a question or comment about. > > > Proposal to move forward: > * Tooling: The preferred tool in last week?s conversation was Matrix - https://matrix.org > - It is an open tool, which ensures continued access to the platform and its features > - It is more modern than IRC > > * Format: The idea came up to create multiple channels for the StarlingX project > - We can keep the all-community channel > - We can create channels for each project team, that are more topic specific > - We also have the option to create a channel for newcomers, which could include troubleshooting type of conversations as well > > > In order to identify next steps, please share your feedback about the proposal above. Ie: What do you think about Matrix? Would you be more comfortable using a chat tool with the more fine grained configuration of having multiple channels? > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Director of Community > Open Infrastructure Foundation > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at eng.windriver.com Thu Jul 20 13:36:39 2023 From: scott.little at eng.windriver.com (Scott.Little) Date: Thu, 20 Jul 2023 09:36:39 -0400 Subject: [Starlingx-discuss] Transition away from CENGN In-Reply-To: References: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> Message-ID: <51e5a036-a6bb-ad55-bbdd-1fc0fb1abfe6@eng.windriver.com> The final CENGN master branch build successful.? Timestamp 20230719T142650Z. Seeing no objections, we'll start enacting the transition plan. Scott On 2023-07-19 10:44, Little, Scott wrote: > Based on the community call, the agreed plan is as follows. > > - Allow the current CENGN master branch build to complete. > - Freeze further build attempts on CENGN as of July 20? 04:00 UTC. > - Final sync of the Wind River mirror relative to the CENGN mirror > starts Jul 20 13:00 UTC > - DNS changed to redirect mirror.starlingx.cengn.ca to > mirror.starlingx.windriver.com Jul 20 16:00 UTC > - Test build(s) of StarlingX in Wind River hardware Jul 20 16:00 UTC- > July 21 20:00 UTC > - July 21 20:00 UTC... If tests are successful, start scheduled builds > on Wind River infrastructure, otherwise revert to CENGN as re-enable > scheduled builds on their side. > > If there are objections to this plan, please speak out today. > > Scott > > > On 2023-07-19 09:24, Little, Scott wrote: >> As you should all be aware by now, StarlingX will be relocating our >> build and mirror service away from CENGN.? The replacement host, at >> least for the near future, will be Wind River.? CENGN has graciously >> offered to redirect traffic referencing mirror.starlingx.cengn.ca to our >> new home at mirror.starlingx.windriver.com for an extended period to >> ease the transition. >> >> The Wind River infrastructure is now ready.? We need to plan a time for >> the transition.? During the transition, we'll need to disable builds for >> a day or two.? This will give us a bit of time to ensure the Wind River >> is fully up to date with the final CENGN content.? We will discuss the >> timing at this weeks community meeting.? If you have concerns, please >> attend. >> >> Scott Little >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From Steven.Webster at windriver.com Thu Jul 20 16:24:23 2023 From: Steven.Webster at windriver.com (Webster, Steven) Date: Thu, 20 Jul 2023 16:24:23 +0000 Subject: [Starlingx-discuss] Minutes: networking sub-team meeting 07-20-23 Message-ID: ======== Next meeting: 08-03-23 Meeting logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings Agenda/Detailed minutes are posted at: https://etherpad.opendev.org/p/stx-networking ======== Feature Updates: Ethernet Operator Support: - Spec is almost approved. There are 2 +2 just needs a bump to integrate it. Intel FEC Operator - Update coming! (end of month) - Ability to change resource name (from intel_fec_acc200, etc.) to something more generic like acc200 - Add igb_uio into default list of default list of supported drivers for VF interface - Enable secure boot + kernel lockdown or not. kernel lockdown = vfio only. Otherwise any of the other 3 drivers. - Another new version of pf-bb-config to 23.03 https://review.opendev.org/c/starlingx/app-sriov-fec-operator/+/888743 https://storyboard.openstack.org/#!/story/2010826 - Switch to UBI 9 base image (rather than CentOS) - Roadmap: Intel to build, host FEC images on their own rather than starlingX building/hosting Bug Updates: One new one: #2020213 ACC100 pod in pending state when vfDriver:igb_uio is configured using sriov-fec-operator -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at eng.windriver.com Thu Jul 20 19:40:55 2023 From: scott.little at eng.windriver.com (Scott.Little) Date: Thu, 20 Jul 2023 15:40:55 -0400 Subject: [Starlingx-discuss] Transition away from CENGN In-Reply-To: <51e5a036-a6bb-ad55-bbdd-1fc0fb1abfe6@eng.windriver.com> References: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> <51e5a036-a6bb-ad55-bbdd-1fc0fb1abfe6@eng.windriver.com> Message-ID: Final sync missed some content.? I've restarted it, but it will run into the evening. We'll delay the DNS change to redirect mirror.starlingx.cengn.ca to mirror.starlingx.windriver.com until Jul 21 13:00 UTC? (9 am Easter) Scott On 2023-07-20 09:36, Scott.Little wrote: > > The final CENGN master branch build successful.? Timestamp > 20230719T142650Z. > > Seeing no objections, we'll start enacting the transition plan. > > Scott > > > On 2023-07-19 10:44, Little, Scott wrote: >> Based on the community call, the agreed plan is as follows. >> >> - Allow the current CENGN master branch build to complete. >> - Freeze further build attempts on CENGN as of July 20? 04:00 UTC. >> - Final sync of the Wind River mirror relative to the CENGN mirror >> starts Jul 20 13:00 UTC >> - DNS changed to redirect mirror.starlingx.cengn.ca to >> mirror.starlingx.windriver.com Jul 20 16:00 UTC >> - Test build(s) of StarlingX in Wind River hardware Jul 20 16:00 UTC- >> July 21 20:00 UTC >> - July 21 20:00 UTC... If tests are successful, start scheduled builds >> on Wind River infrastructure, otherwise revert to CENGN as re-enable >> scheduled builds on their side. >> >> If there are objections to this plan, please speak out today. >> >> Scott >> >> >> On 2023-07-19 09:24, Little, Scott wrote: >>> As you should all be aware by now, StarlingX will be relocating our >>> build and mirror service away from CENGN.? The replacement host, at >>> least for the near future, will be Wind River.? CENGN has graciously >>> offered to redirect traffic referencing mirror.starlingx.cengn.ca to >>> our >>> new home at mirror.starlingx.windriver.com for an extended period to >>> ease the transition. >>> >>> The Wind River infrastructure is now ready.? We need to plan a time for >>> the transition.? During the transition, we'll need to disable builds >>> for >>> a day or two.? This will give us a bit of time to ensure the Wind River >>> is fully up to date with the final CENGN content.? We will discuss the >>> timing at this weeks community meeting.? If you have concerns, please >>> attend. >>> >>> Scott Little >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From Rogerio.Ferraz at encora.com Thu Jul 20 20:03:16 2023 From: Rogerio.Ferraz at encora.com (Rogerio Oliveira Ferraz) Date: Thu, 20 Jul 2023 20:03:16 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 62, Issue 39 In-Reply-To: References: Message-ID: +1 ________________________________ From: starlingx-discuss-request at lists.starlingx.io Sent: Thursday, July 20, 2023 3:29 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 62, Issue 39 External Mail: Do not click links or open attachments unless you recognize the sender and know the content is safe. Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.starlingx.io%2Fcgi-bin%2Fmailman%2Flistinfo%2Fstarlingx-discuss&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453256381%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eLNUYNWnu7peedmrqvXWSwJDsEcPQIVBACzjPhlBsRM%3D&reserved=0 or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Community Communication Channels - VOTE NEEDED (Ildiko Vancsa) 2. Re: Starlingx-discuss Digest, Vol 62, Issue 38 (Liu, David) 3. Re: Community Communication Channels - VOTE NEEDED (Jaiswal, Abhishek) ---------------------------------------------------------------------- Message: 1 Date: Wed, 19 Jul 2023 14:45:20 -0700 From: Ildiko Vancsa To: StarlingX ML Subject: Re: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED Message-ID: Content-Type: text/plain; charset=utf-8 Hi StarlingX Community, Thank you to everyone who already voted. For those who haven?t had the chance yet, it is a friendly reminder to please share your vote about moving to Matrix, to use it as the official chat tool for community communications. Please respond with ?+1?, if you are in support, or share your concerns, if there is any. Please hit ?reply all? to keep the mailing list in the thread with your response. I will share the results of the vote early next week, and propose next steps for the TSC to approve. Please let me know if you have any questions. Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 17, 2023, at 12:38, Chris Friesen wrote: > > +1, willing to give it a try. > > On 7/12/2023 5:14 PM, Ildiko Vancsa wrote: >> CAUTION: This email comes from a non Wind River email account! >> Do not click links or open attachments unless you recognize the sender and know the content is safe. >> >> Hi, >> >> Thank you all for the feedback so far! >> >> I haven?t received any objections against the option to start using Matrix as a chat tool for the StarlingX community. People had questions on the Community Call about the tool today, so I collected some useful information to help exploring it: >> >> - As a reminder, you can find out more about the tool here: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatrix.org%2F&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453256381%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EMkaWTExXPpD4xVg9dsig%2BrLzbvkcc%2FskBRRaruO5rA%3D&reserved=0 >> - There are different options to use as a browser or desktop client. Many of them are also available on smartphones. >> + I?m using Element - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Felement.io%2F&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453256381%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NsqoRes5jW3a4haSCY%2BEJHwuuOIYZOXYLShILK1iugo%3D&reserved=0 >> + Some other options include >> ~ Weechat - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpoljar%2Fweechat-matrix&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453256381%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zM0fcLGffA9%2FjQHJdx52WDyfxLbpiAxlSqKs8TjGB4A%3D&reserved=0 >> ~ SchildiChat - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fschildi.chat%2F&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453256381%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8RDfby0SaHWQtJ5nm9qyDdrm22IVdTC%2FDbnNXCjKE%2BU%3D&reserved=0 >> ~ FluffyChat - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffluffychat.im%2F&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453256381%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=VN46IN5kUoe5nVApu57vbYPhI6dechlXNZxhnAKI230%3D&reserved=0 >> >> - The #starlingX IRC channel is also available through Matrix - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatrix.to%2F%23%2F!XDOJNehPiaWKvYGWVD%3Amatrix.org%3Fvia%3Dmatrix.org&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453256381%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=NopvUR1ecGiHDdOC2IWqmXeoc9EoY1LwzE9G%2FKmgL2o%3D&reserved=0 >> ~ You will need to create an account first >> ~ There is documentation available in the Zuul community?s docs about how to register - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzuul-ci.org%2Fdocs%2Fzuul%2Flatest%2Fhowtos%2Fmatrix.html%23create-an-account&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453256381%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=sJxVFFns6aTH3n3UNq0%2F4h9LxUEJcOVv9LLe9IzSx2I%3D&reserved=0 >> >> >> During the Community Call, it also came up that it would be great to agree on how we would like to utilize a chat tool. For instance, to aovid having too many channels, etc. The current proposal to the Matrix setup is the following: >> >> - Have multiple chat rooms available for community communication: >> + starlingx-general room - topics that are relevant to the whole community >> + StarlingX project team channels >> ~ topics that are relevant to a project team >> ~ ie: starlingx-build, starlingx-containers, etc >> + Optional channel ideas - specific topic areas that are outside of the existing project teams >> ~ starlingx-newcomers >> ~ starlingx-troubleshooting >> >> >> __ If you are in support to use Matrix as the chat tool for StarlingX moving forward, please reply to this email with ?+1?.__ >> >> >> Please let me know if you have any questions, or if you need help with setting up Matrix. >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Director of Community >> Open Infrastructure Foundation >> >> >> >> >> >>> On Jul 4, 2023, at 21:42, open infra wrote: >>> >>> CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord. >>> Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply). >>> >>> >>> >>> >>> >>> On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa wrote: >>> Hi StarlingX Community, >>> >>> I?m reaching out to you about a recurring topic that came up during the PTG last week again. >>> >>> While the community is actively using the mailing list, it is not always the best platform, as it doesn?t allow for more synchronous chat. Contributors at the event had a growing interest in finding a way to provide the opportunity for more synchronous communication to capture the project teams? chatters, and enable newcomers to reach out and start to participate. >>> >>> Challenges: >>> * Tooling: People raised that while it is an open protocol, IRC still doesn?t feel inclusive due to its simplicity. >>> * Format: The current one-channel setup doesn?t feel efficient and comfortable, since people need to address everyone in the channel with every topic they have a question or comment about. >>> >>> >>> Proposal to move forward: >>> * Tooling: The preferred tool in last week?s conversation was Matrix - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatrix.org%2F&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453256381%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EMkaWTExXPpD4xVg9dsig%2BrLzbvkcc%2FskBRRaruO5rA%3D&reserved=0 >>> - It is an open tool, which ensures continued access to the platform and its features >>> - It is more modern than IRC >>> >>> * Format: The idea came up to create multiple channels for the StarlingX project >>> - We can keep the all-community channel >>> - We can create channels for each project team, that are more topic specific >>> - We also have the option to create a channel for newcomers, which could include troubleshooting type of conversations as well >>> >>> >>> In order to identify next steps, please share your feedback about the proposal above. Ie: What do you think about Matrix? Would you be more comfortable using a chat tool with the more fine grained configuration of having multiple channels? >>> >>> Thanks and Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Director of Community >>> Open Infrastructure Foundation >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > ------------------------------ Message: 2 Date: Thu, 20 Jul 2023 03:08:05 +0000 From: "Liu, David" To: "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Starlingx-discuss Digest, Vol 62, Issue 38 Message-ID: Content-Type: text/plain; charset="us-ascii" Hi, I'm working on submit some code for review, and the zuul gate job failed, but I can't download the detailed logs, is there a problem with The CI server side? My zuul job is here: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzuul.opendev.org%2Ft%2Fopenstack%2Fbuild%2F760e0e486b024f9c9e5c5883af49299c%2Fartifacts&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453256381%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fkDaghBo3FJ14mESxlptBUYAl%2B%2FTGmzaAQDQdlwEKlk%3D&reserved=0 Thanks, David -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Thursday, July 20, 2023 1:03 AM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 62, Issue 38 CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.starlingx.io%2Fcgi-bin%2Fmailman%2Flistinfo%2Fstarlingx-discuss&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453256381%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=eLNUYNWnu7peedmrqvXWSwJDsEcPQIVBACzjPhlBsRM%3D&reserved=0 or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Apt-ostree repository (Short, Charles) ---------------------------------------------------------------------- Message: 1 Date: Wed, 19 Jul 2023 17:02:46 +0000 From: "Short, Charles" To: "Waines, Greg" , "starlingx-discuss at lists.starlingx.io" Subject: Re: [Starlingx-discuss] Apt-ostree repository Message-ID: Content-Type: text/plain; charset="us-ascii" Hi Answers are in line. From: Waines, Greg Sent: Wednesday, July 19, 2023 12:52 PM To: Short, Charles ; starlingx-discuss at lists.starlingx.io Subject: RE: Apt-ostree repository Hey Chuck, I know we talked about this offline and it was also discussed in today's StarlingX Community meeting ... Just to clarify / add-some-detail to your request ... for community understanding ... * 'apt-ostree' is sort of a hybrid package manager that allows one to build and manage ostree commits based on DEB PKGs Correct it will become a hybrid image/package manager that allows to build and manage ostree commits based on Debian packages. * You are developing this as part of the FLOCK project team's work on 'Software Upgrade/Update Evolution', see stx 9 feature plan spreadsheet https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fspreadsheets%2Fd%2F1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w%2Fedit%23gid%3D1107209846&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453412513%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Dbkkm4vsJznHL5Zl3dRa%2FhgVIgMuYP%2Ft273kcGdP6co%3D&reserved=0 . Correct * * Your development plans for apt-ostree is to develop this generically (i.e. no starlingx specifics), using the debian apt package manager and debian's ostree package. That's correct I see possible use cases outside of StarlingX where it could possibly be used for example embedded systems for managing updates, installs, etc. * AND THEN the higher-level StarlingX-specific Software Management code would USE apt-ostree StarlingX manages large number of nodes well. I would hope that apt-ostree gets to the point where apt-ostree can manage Debian based systems well. * * As discussed, our long term plans would be to offer/propose this as a debian package to the debian community .... Rather than bury this in starlingx. * And then we would just include this new debian package in our host packages and use it for starlingx Correct I would like to start with small and then work our way through a bigger use case within the Debian community. * * In the meantime, you're proposing that we create an apt-ostree repo in starlingx, as sort of an incubation period ... in order to develop apt-ostree and meet stx 9 release schedules. * With the intent to move it to the debian community later. Correct Greg. p.s. I'm a +1 for new short-term apt-ostree repo From: Short, Charles > Sent: Tuesday, July 18, 2023 4:08 PM To: starlingx-discuss at lists.starlingx.io Subject: [Starlingx-discuss] Apt-ostree repository Hi, I been working on a Debian based ostree package management system for the past couple of months. It is similar to how rpm-ostree manages packages with ostree on Fedora. I was wondering if there were any objections to adding the repository to the starlingx namespace on opendev.org?> Thanks chuck -------------- next part -------------- An HTML attachment was scrubbed... URL: > ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io ------------------------------ End of Starlingx-discuss Digest, Vol 62, Issue 38 ************************************************* ------------------------------ Message: 3 Date: Thu, 20 Jul 2023 06:29:08 +0000 From: "Jaiswal, Abhishek" To: Ildiko Vancsa , StarlingX ML Subject: Re: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED Message-ID: Content-Type: text/plain; charset="utf-8" +1 Abhishek Jaiswal Member of Technical Staff M/?+91 7799126262 -----Original Message----- From: Ildiko Vancsa Sent: Thursday, July 20, 2023 3:15 AM To: StarlingX ML Subject: Re: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, Thank you to everyone who already voted. For those who haven?t had the chance yet, it is a friendly reminder to please share your vote about moving to Matrix, to use it as the official chat tool for community communications. Please respond with ?+1?, if you are in support, or share your concerns, if there is any. Please hit ?reply all? to keep the mailing list in the thread with your response. I will share the results of the vote early next week, and propose next steps for the TSC to approve. Please let me know if you have any questions. Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 17, 2023, at 12:38, Chris Friesen wrote: > > +1, willing to give it a try. > > On 7/12/2023 5:14 PM, Ildiko Vancsa wrote: >> CAUTION: This email comes from a non Wind River email account! >> Do not click links or open attachments unless you recognize the sender and know the content is safe. >> >> Hi, >> >> Thank you all for the feedback so far! >> >> I haven?t received any objections against the option to start using Matrix as a chat tool for the StarlingX community. People had questions on the Community Call about the tool today, so I collected some useful information to help exploring it: >> >> - As a reminder, you can find out more about the tool here: https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatrix.org%2F&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453412513%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=iBJ0ahPiawRo051ThlK4SfNUmbvZ6iLLm9NQnh2e38I%3D&reserved=0 >> - There are different options to use as a browser or desktop client. Many of them are also available on smartphones. >> + I?m using Element - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Felement.io%2F&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453412513%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=boM7m3HacHvn23zVWOekKdJK4g3RoL%2BKzunqkIpy43Q%3D&reserved=0 >> + Some other options include >> ~ Weechat - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpoljar%2Fweechat-matrix&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453412513%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=AUMOHVVih8UItZqLQROzQeKDaGrfeKqdXErKRCzIgYM%3D&reserved=0 >> ~ SchildiChat - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fschildi.chat%2F&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453412513%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GrHzL3KOMzxYMe8Q2vj8IXMm5fbV%2FQwUZ7yvGkrD3rg%3D&reserved=0 >> ~ FluffyChat - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffluffychat.im%2F&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453412513%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=f1jshr5%2BY1SkPGqs0%2B8hOwZxWSlFXaUjPc6VBgr8khQ%3D&reserved=0 >> >> - The #starlingX IRC channel is also available through Matrix - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatrix.to%2F%23%2F!XDOJNehPiaWKvYGWVD%3Amatrix.org%3Fvia%3Dmatrix.org&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453412513%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=AuRTgdtvynN9%2Fgqymdvnf86mlsdyBGLb6%2BrJhzp1vi4%3D&reserved=0 >> ~ You will need to create an account first >> ~ There is documentation available in the Zuul community?s docs about how to register - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fzuul-ci.org%2Fdocs%2Fzuul%2Flatest%2Fhowtos%2Fmatrix.html%23create-an-account&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453412513%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9RYkngoqLUk16UO1IUj9ZEbOYC3yj8uJ9%2F%2FZ9503fmg%3D&reserved=0 >> >> >> During the Community Call, it also came up that it would be great to agree on how we would like to utilize a chat tool. For instance, to aovid having too many channels, etc. The current proposal to the Matrix setup is the following: >> >> - Have multiple chat rooms available for community communication: >> + starlingx-general room - topics that are relevant to the whole community >> + StarlingX project team channels >> ~ topics that are relevant to a project team >> ~ ie: starlingx-build, starlingx-containers, etc >> + Optional channel ideas - specific topic areas that are outside of the existing project teams >> ~ starlingx-newcomers >> ~ starlingx-troubleshooting >> >> >> __ If you are in support to use Matrix as the chat tool for StarlingX moving forward, please reply to this email with ?+1?.__ >> >> >> Please let me know if you have any questions, or if you need help with setting up Matrix. >> >> Best Regards, >> Ildik? >> >> ??? >> >> Ildik? V?ncsa >> Director of Community >> Open Infrastructure Foundation >> >> >> >> >> >>> On Jul 4, 2023, at 21:42, open infra wrote: >>> >>> CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord. >>> Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply). >>> >>> >>> >>> >>> >>> On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa wrote: >>> Hi StarlingX Community, >>> >>> I?m reaching out to you about a recurring topic that came up during the PTG last week again. >>> >>> While the community is actively using the mailing list, it is not always the best platform, as it doesn?t allow for more synchronous chat. Contributors at the event had a growing interest in finding a way to provide the opportunity for more synchronous communication to capture the project teams? chatters, and enable newcomers to reach out and start to participate. >>> >>> Challenges: >>> * Tooling: People raised that while it is an open protocol, IRC still doesn?t feel inclusive due to its simplicity. >>> * Format: The current one-channel setup doesn?t feel efficient and comfortable, since people need to address everyone in the channel with every topic they have a question or comment about. >>> >>> >>> Proposal to move forward: >>> * Tooling: The preferred tool in last week?s conversation was Matrix - https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmatrix.org%2F&data=05%7C01%7Crogerio.ferraz%40encora.com%7C1be55554a189430fb99408db88ead6f2%7C1e0c92b0f1bd441ebbe6c778f9ced553%7C0%7C0%7C638254314453412513%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=iBJ0ahPiawRo051ThlK4SfNUmbvZ6iLLm9NQnh2e38I%3D&reserved=0 >>> - It is an open tool, which ensures continued access to the platform and its features >>> - It is more modern than IRC >>> >>> * Format: The idea came up to create multiple channels for the StarlingX project >>> - We can keep the all-community channel >>> - We can create channels for each project team, that are more topic specific >>> - We also have the option to create a channel for newcomers, which could include troubleshooting type of conversations as well >>> >>> >>> In order to identify next steps, please share your feedback about the proposal above. Ie: What do you think about Matrix? Would you be more comfortable using a chat tool with the more fine grained configuration of having multiple channels? >>> >>> Thanks and Best Regards, >>> Ildik? >>> >>> ??? >>> >>> Ildik? V?ncsa >>> Director of Community >>> Open Infrastructure Foundation >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io ------------------------------ End of Starlingx-discuss Digest, Vol 62, Issue 39 ************************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From David.Liu at windriver.com Fri Jul 21 01:43:19 2023 From: David.Liu at windriver.com (Liu, David) Date: Fri, 21 Jul 2023 01:43:19 +0000 Subject: [Starlingx-discuss] Starlingx-discuss Digest, Vol 62, Issue 41 In-Reply-To: References: Message-ID: Hi Jeremy, Thank you for providing feedbacks, for the log access, I think it's my network problem. Yes, I'll try to fix as your solution pointed. Regards, David -----Original Message----- From: starlingx-discuss-request at lists.starlingx.io Sent: Thursday, July 20, 2023 9:20 PM To: starlingx-discuss at lists.starlingx.io Subject: Starlingx-discuss Digest, Vol 62, Issue 41 CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Send Starlingx-discuss mailing list submissions to starlingx-discuss at lists.starlingx.io To subscribe or unsubscribe via the World Wide Web, visit https://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss or, via email, send a message with subject or body 'help' to starlingx-discuss-request at lists.starlingx.io You can reach the person managing the list at starlingx-discuss-owner at lists.starlingx.io When replying, please edit your Subject line so it is more specific than "Re: Contents of Starlingx-discuss digest..." Today's Topics: 1. Re: Starlingx-discuss Digest, Vol 62, Issue 38 (Jeremy Stanley) 2. Re: Community Communication Channels - VOTE NEEDED (Cervi, Thales Elero) ---------------------------------------------------------------------- Message: 1 Date: Thu, 20 Jul 2023 12:32:29 +0000 From: Jeremy Stanley To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Starlingx-discuss Digest, Vol 62, Issue 38 Message-ID: <20230720123228.fzrsixloayxl5hbf at yuggoth.org> Content-Type: text/plain; charset="us-ascii" On 2023-07-20 03:08:05 +0000 (+0000), Liu, David wrote: > I'm working on submit some code for review, and the zuul gate job > failed, but I can't download the detailed logs, is there a problem > with The CI server side? > > My zuul job is here: > https://zuul.opendev.org/t/openstack/build/760e0e486b024f9c9e5c5883af4 > 9299c/artifacts [...] I'm not sure what logs you think are missing, but the console log there shows that the pyflakes static analysis tool you're running encountered a fatal exception: AttributeError: 'FlakesChecker' object has no attribute 'JOINEDSTR' https://zuul.opendev.org/t/openstack/build/760e0e486b024f9c9e5c5883af49299c/log/job-output.txt#670 I'm able to reproduce this by checking out your change and running `tox -e pep8 -c distributedcloud-client/tox.ini` under python3.7, while running the same with a fresh checkout of the master branch completes successfully, so there's definitely something about https://review.opendev.org/888424 which is triggering the problem. A quick web search on the exact error string turns up this mailing list thread from 2019 about incompatibilities between the hacking plugin and (then) newer flake8/pyflakes versions: https://lists.openstack.org/pipermail/openstack-discuss/2019-November/011027.html My best guess, without digging deeper, is that something in the code being added in change 888424 is tickling the necessary code paths through pyflakes to hit the incompatibility with hacking. Indeed, editing distributedcloud-client/test-requirements.txt and bluntly replacing the hacking entry with just flake8 gets it to succeed, but of course this is only a reasonable solution if you don't care about the additional rules that module was enforcing. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: ------------------------------ Message: 2 Date: Thu, 20 Jul 2023 13:20:11 +0000 From: "Cervi, Thales Elero" To: Ildiko Vancsa , StarlingX ML Subject: Re: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED Message-ID: Content-Type: text/plain; charset="utf-8" +1 for matrix ________________________________ From: Ildiko Vancsa Sent: Wednesday, July 12, 2023 8:14 PM To: StarlingX ML Subject: Re: [Starlingx-discuss] Community Communication Channels - VOTE NEEDED CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi, Thank you all for the feedback so far! I haven?t received any objections against the option to start using Matrix as a chat tool for the StarlingX community. People had questions on the Community Call about the tool today, so I collected some useful information to help exploring it: - As a reminder, you can find out more about the tool here: https://matrix.org - There are different options to use as a browser or desktop client. Many of them are also available on smartphones. + I?m using Element - https://element.io + Some other options include ~ Weechat - https://github.com/poljar/weechat-matrix ~ SchildiChat - https://schildi.chat/ ~ FluffyChat - https://fluffychat.im/ - The #starlingX IRC channel is also available through Matrix - https://matrix.to/#/!XDOJNehPiaWKvYGWVD:matrix.org?via=matrix.org ~ You will need to create an account first ~ There is documentation available in the Zuul community?s docs about how to register - https://zuul-ci.org/docs/zuul/latest/howtos/matrix.html#create-an-account During the Community Call, it also came up that it would be great to agree on how we would like to utilize a chat tool. For instance, to aovid having too many channels, etc. The current proposal to the Matrix setup is the following: - Have multiple chat rooms available for community communication: + starlingx-general room - topics that are relevant to the whole community + StarlingX project team channels ~ topics that are relevant to a project team ~ ie: starlingx-build, starlingx-containers, etc + Optional channel ideas - specific topic areas that are outside of the existing project teams ~ starlingx-newcomers ~ starlingx-troubleshooting __ If you are in support to use Matrix as the chat tool for StarlingX moving forward, please reply to this email with ?+1?.__ Please let me know if you have any questions, or if you need help with setting up Matrix. Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 4, 2023, at 21:42, open infra wrote: > > CentOS, TDF/LibreOffice, and Libre Graphics use Libra Chat and Scala, and many others use discord. > Fedora and many others use metrix. I think its better switch to metrix as as the OpenDev Collaboratory has a metrix server (.as Jeremy Stanley mentioned in his reply). > > > > > > On Thu, Jun 22, 2023 at 11:34?PM Ildiko Vancsa wrote: > Hi StarlingX Community, > > I?m reaching out to you about a recurring topic that came up during the PTG last week again. > > While the community is actively using the mailing list, it is not always the best platform, as it doesn?t allow for more synchronous chat. Contributors at the event had a growing interest in finding a way to provide the opportunity for more synchronous communication to capture the project teams? chatters, and enable newcomers to reach out and start to participate. > > Challenges: > * Tooling: People raised that while it is an open protocol, IRC still doesn?t feel inclusive due to its simplicity. > * Format: The current one-channel setup doesn?t feel efficient and comfortable, since people need to address everyone in the channel with every topic they have a question or comment about. > > > Proposal to move forward: > * Tooling: The preferred tool in last week?s conversation was Matrix - https://matrix.org > - It is an open tool, which ensures continued access to the platform and its features > - It is more modern than IRC > > * Format: The idea came up to create multiple channels for the StarlingX project > - We can keep the all-community channel > - We can create channels for each project team, that are more topic specific > - We also have the option to create a channel for newcomers, which > could include troubleshooting type of conversations as well > > > In order to identify next steps, please share your feedback about the proposal above. Ie: What do you think about Matrix? Would you be more comfortable using a chat tool with the more fine grained configuration of having multiple channels? > > Thanks and Best Regards, > Ildik? > > ??? > > Ildik? V?ncsa > Director of Community > Open Infrastructure Foundation > > > > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Subject: Digest Footer _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io ------------------------------ End of Starlingx-discuss Digest, Vol 62, Issue 41 ************************************************* From Venkata.Veldanda at radisys.com Fri Jul 21 04:07:42 2023 From: Venkata.Veldanda at radisys.com (Venkata Ramana Veldanda) Date: Fri, 21 Jul 2023 04:07:42 +0000 Subject: [Starlingx-discuss] Packet Mirroring Capability on Stx Message-ID: Hello Team, In a std k8s environment on an open source linux, we were able to perform packet mirroring on a mirrored VF by configuring ingress & egress in the respective PCI device files. However, it appears that on some of the NICs like E810 (CVL) this support doesn't seem to be available. The main reason we were attempting this to avoid tracing directly a dpdk fastpkt interface (either on fronthaul or midhual) was to mirror the VF device and capture through wireshark on the mirrored interface. However, the question is does StarlingX provide any in-house tool to capture the packets for the above requirement irrespective of the NIC model etc?. Regards, Venkata Veldanda -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Fri Jul 21 17:18:01 2023 From: scott.little at windriver.com (Scott Little) Date: Fri, 21 Jul 2023 13:18:01 -0400 Subject: [Starlingx-discuss] Transition away from CENGN In-Reply-To: References: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> <51e5a036-a6bb-ad55-bbdd-1fc0fb1abfe6@eng.windriver.com> Message-ID: We encountered SSL certificate issues after transition.? We have reverted to the DNS to the CENGN server.? We'll try to get the certificated sorted out Monday. I'm thinking we should leave CENGN builds disabled over the weekend, so that we don't have to go through another sync cycle with the new server.? What does the community think?? Do we need a weekend build? Scott On 2023-07-20 15:40, Scott.Little wrote: > Final sync missed some content.? I've restarted it, but it will run > into the evening. > > We'll delay the DNS change to redirect mirror.starlingx.cengn.ca to > mirror.starlingx.windriver.com until Jul 21 13:00 UTC? (9 am Easter) > > Scott > > On 2023-07-20 09:36, Scott.Little wrote: >> >> The final CENGN master branch build successful.? Timestamp >> 20230719T142650Z. >> >> Seeing no objections, we'll start enacting the transition plan. >> >> Scott >> >> >> On 2023-07-19 10:44, Little, Scott wrote: >>> Based on the community call, the agreed plan is as follows. >>> >>> - Allow the current CENGN master branch build to complete. >>> - Freeze further build attempts on CENGN as of July 20? 04:00 UTC. >>> - Final sync of the Wind River mirror relative to the CENGN mirror >>> starts Jul 20 13:00 UTC >>> - DNS changed to redirect mirror.starlingx.cengn.ca to >>> mirror.starlingx.windriver.com Jul 20 16:00 UTC >>> - Test build(s) of StarlingX in Wind River hardware Jul 20 16:00 UTC- >>> July 21 20:00 UTC >>> - July 21 20:00 UTC... If tests are successful, start scheduled builds >>> on Wind River infrastructure, otherwise revert to CENGN as re-enable >>> scheduled builds on their side. >>> >>> If there are objections to this plan, please speak out today. >>> >>> Scott >>> >>> >>> On 2023-07-19 09:24, Little, Scott wrote: >>>> As you should all be aware by now, StarlingX will be relocating our >>>> build and mirror service away from CENGN.? The replacement host, at >>>> least for the near future, will be Wind River.? CENGN has graciously >>>> offered to redirect traffic referencing mirror.starlingx.cengn.ca >>>> to our >>>> new home at mirror.starlingx.windriver.com for an extended period to >>>> ease the transition. >>>> >>>> The Wind River infrastructure is now ready.? We need to plan a time >>>> for >>>> the transition.? During the transition, we'll need to disable >>>> builds for >>>> a day or two.? This will give us a bit of time to ensure the Wind >>>> River >>>> is fully up to date with the final CENGN content.? We will discuss the >>>> timing at this weeks community meeting.? If you have concerns, please >>>> attend. >>>> >>>> Scott Little >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From Robert.Church at windriver.com Fri Jul 21 17:40:46 2023 From: Robert.Church at windriver.com (Church, Robert) Date: Fri, 21 Jul 2023 17:40:46 +0000 Subject: [Starlingx-discuss] Transition away from CENGN In-Reply-To: References: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> <51e5a036-a6bb-ad55-bbdd-1fc0fb1abfe6@eng.windriver.com> Message-ID: +1 for whatever you think is the quickest way to get the transition completed. From: Scott Little Date: Friday, July 21, 2023 at 12:22 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Transition away from CENGN We encountered SSL certificate issues after transition. We have reverted to the DNS to the CENGN server. We'll try to get the certificated sorted out Monday. I'm thinking we should leave CENGN builds disabled over the weekend, so that we don't have to go through another sync cycle with the new server. What does the community think? Do we need a weekend build? Scott On 2023-07-20 15:40, Scott.Little wrote: > Final sync missed some content. I've restarted it, but it will run > into the evening. > > We'll delay the DNS change to redirect mirror.starlingx.cengn.ca to > mirror.starlingx.windriver.com until Jul 21 13:00 UTC (9 am Easter) > > Scott > > On 2023-07-20 09:36, Scott.Little wrote: >> >> The final CENGN master branch build successful. Timestamp >> 20230719T142650Z. >> >> Seeing no objections, we'll start enacting the transition plan. >> >> Scott >> >> >> On 2023-07-19 10:44, Little, Scott wrote: >>> Based on the community call, the agreed plan is as follows. >>> >>> - Allow the current CENGN master branch build to complete. >>> - Freeze further build attempts on CENGN as of July 20 04:00 UTC. >>> - Final sync of the Wind River mirror relative to the CENGN mirror >>> starts Jul 20 13:00 UTC >>> - DNS changed to redirect mirror.starlingx.cengn.ca to >>> mirror.starlingx.windriver.com Jul 20 16:00 UTC >>> - Test build(s) of StarlingX in Wind River hardware Jul 20 16:00 UTC- >>> July 21 20:00 UTC >>> - July 21 20:00 UTC... If tests are successful, start scheduled builds >>> on Wind River infrastructure, otherwise revert to CENGN as re-enable >>> scheduled builds on their side. >>> >>> If there are objections to this plan, please speak out today. >>> >>> Scott >>> >>> >>> On 2023-07-19 09:24, Little, Scott wrote: >>>> As you should all be aware by now, StarlingX will be relocating our >>>> build and mirror service away from CENGN. The replacement host, at >>>> least for the near future, will be Wind River. CENGN has graciously >>>> offered to redirect traffic referencing mirror.starlingx.cengn.ca >>>> to our >>>> new home at mirror.starlingx.windriver.com for an extended period to >>>> ease the transition. >>>> >>>> The Wind River infrastructure is now ready. We need to plan a time >>>> for >>>> the transition. During the transition, we'll need to disable >>>> builds for >>>> a day or two. This will give us a bit of time to ensure the Wind >>>> River >>>> is fully up to date with the final CENGN content. We will discuss the >>>> timing at this weeks community meeting. If you have concerns, please >>>> attend. >>>> >>>> Scott Little >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Juanita.Balaraj at windriver.com Fri Jul 21 19:32:05 2023 From: Juanita.Balaraj at windriver.com (Balaraj, Juanita) Date: Fri, 21 Jul 2023 19:32:05 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 07-20-2023 In-Reply-To: References: Message-ID: Hello All, Here are this week's docs team meeting minutes (short form). Details in [2]. NOTE: Join us if you have interest in StarlingX docs! We meet on Fridays at 6.00 a.m. PST. (Please note the new change) [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Juanita Balaraj ============ 20 July-23 Note: From July 1st week the StarlingX DOC meetings will be switching over to Fridays 6.00 a.m. PST to accommodate other time zones. See https://wiki.openstack.org/wiki/Starlingx/Meetings for more details. Status: - Stx 9.0 Release Tracking Spreadsheet: Doc Stories are tracked in https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing. - To add stories that are planned for Stx 9.0 - AR Juanita - WIP - Update the "Install StarlingX Kuberbetes in a virtual environment" docs; https://docs.starlingx.io/r/stx.8.0/deploy_install_guides/release/index-install-r7-8966076f0e81.html - Greg to create a LP bug - DONE ; https://bugs.launchpad.net/starlingx/+bug/2028272 : Bugs : StarlingX (launchpad.net) - Discussion about Merging the Installation Guides ; Virtual env with the Bare metal docs. - Split the docs and retain them as separate guides at a high level. Resue content from Bare Metal in the Virtual env docs. - Opensource Project versions - Add Opensource Project versions in the Stx 9.0 RN - AR Juanita - Create a story to track and update. Gerrit Reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - To be reviewed and merged - Bruno Muniz / Gustavo Herzmann created a gerrit review to use the automated script for Vbox installs: To raise LP Bugs / Stories; https://storyboard.openstack.org/#!/story/2005051#comment-203593; Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 10 outstanding bugs - The DOC team to create LP defects corresponding with any DS defects - WIP. Teams to add all the impacted Releases when raising a LP bug - Bug #1932314 "Virtual AIO-SX install documentation presents data..." : Bugs : StarlingX (launchpad.net) - To discuss with Greg - DONE Miscellaneous Updates: - We have a fault that is preventing LPs from closing when the coorsponding Gerrit WFs. Ron spoke with Jeremy Stanley, who reproduced the bug and is investigating. - Ron to update the Verified H/W page with the automated script updates https://www.windriver.com/studio/operator/self-validated-and-certified-hosts# - Currently Commented out - Script needs to be updated- Waiting for updates to the script -AR Ron - Bruno Muniz showed interest in creating DOC Videos supporting the StarlingX Installation Process. To check with Ildiko / Greg whether this is ok. These Videos can be hosted in a location in StarlingX. The Installation Docs can point to these videos - AR Bruno to get approvals from Ildiko / Greg - Sphinx Tools - Need to have further discussions about the version used upstream vs. downstream - AR Ron -To determine version. - Docker Container upstream / downstream - AR Ron (Discuss it with Greg / Ildiko) - a long term project - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) - OpenInfra Summit & PTG Recording: https://ptg.opendev.org/etherpads.html - Workshop Details are tracked in https://etherpad.opendev.org/p/stx_hands_on_workshop_2023 - IRC: (Note: This option is being evaluated) IRC channel for communication with the community. Team can use https://www.icechat.net/site/icechat-9/ as an alternate text editor from their browser. IRC is a chat platform, for text-based communication. There's a web client for easy access: https://webchat.oftc.net/- You need to pick a nickname, and the channel name is #opendev. Once you are in the #opendev channel, you can talk to the group of people in that channel. To Setup IRC - contributor-guide documentation (openstack.org) IRC here: https://docs.openstack.org/contributors/common/irc.html; Engineering Status: StarlingX Eng Stx Status: https://etherpad.opendev.org/p/stx-status StarlingX Eng Status 2023 https://etherpad.opendev.org/p/stx-cores ____________________ 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 kennelson11 at gmail.com Mon Jul 24 04:35:57 2023 From: kennelson11 at gmail.com (Kendall Nelson) Date: Sun, 23 Jul 2023 23:35:57 -0500 Subject: [Starlingx-discuss] Fwd: vPTG October 2023 Team Signup Kickoff In-Reply-To: References: Message-ID: Hi Everyone, Hopefully, you have seen by now that the next OpenInfra vPTG[1] which will take place October 23-27, 2023 virtually and registration is open[2]! *To sign up your team, you must complete the survey[3] by August 20th at 7:00 UTC.* We NEED accurate contact information (email and IRC nickname ideally) for the moderator of your team?s sessions. This is because the survey information will be used to organize the schedule sign ups which will be done via the PTGBot. If you are not on IRC, please get setup[4] on the OFTC network and join #openinfra-events. You are also encouraged to familiarize yourself with the PTGBot documentation[5] as well. If you have any questions, please reach out! Information about signing up for time will be sent to moderators late August after the interest survey deadline on August 20. -Kendall (diablo_rojo) [1] PTG Site: https://openinfra.dev/ptg/ [2] PTG Registration: http://ptg2023.openinfra.dev/ [3] Team Survey: https://openinfrafoundation.formstack.com/forms/oct2023_ptg_team_signup [4] Setup IRC: https://docs.openstack.org/contributors/common/irc.html [5] PTGBot README: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst -------------- next part -------------- An HTML attachment was scrubbed... URL: From helena at openinfra.dev Mon Jul 24 13:27:27 2023 From: helena at openinfra.dev (Helena Spease) Date: Mon, 24 Jul 2023 15:27:27 +0200 Subject: [Starlingx-discuss] Take the StarlingX User Survey! Message-ID: <70815FAC-393E-42FB-871B-DBA4483822B2@openinfra.dev> Hello everyone, It?s User Survey season! The 2023 StarlingX User Survey is closing August 23, 2023. That?s just under a month to submit your anonymized feedback to the upstream contributors. https://openinfrafoundation.formstack.com/forms/starlingx_user_survey We have posts from the OpenInfra Foundation social media channels that you can re-share to your networks to encourage them to participate in the User Survey as well. Mastodon: https://social.openinfra.dev/@StarlingX/110769141215695668 Twitter: https://twitter.com/starlingx/status/1683459240185278464 Evaluating another OpenInfra project? We have User Surveys for them as well! Kata Containers: https://openinfrafoundation.formstack.com/forms/kata_containers_user_survey OpenStack: https://www.openstack.org/user-survey/survey-2023/landing StarlingX: https://openinfrafoundation.formstack.com/forms/starlingx_user_survey Zuul: https://openinfrafoundation.formstack.com/forms/zuul_user_survey Cheers, Helena helena at openinfra.dev Marketing & Community Coordinator The OpenInfra Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at eng.windriver.com Mon Jul 24 14:49:35 2023 From: scott.little at eng.windriver.com (Scott.Little) Date: Mon, 24 Jul 2023 10:49:35 -0400 Subject: [Starlingx-discuss] Transition away from CENGN In-Reply-To: References: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> <51e5a036-a6bb-ad55-bbdd-1fc0fb1abfe6@eng.windriver.com> Message-ID: <4cd18adf-bce1-d339-a0d6-6c653d03274e@eng.windriver.com> The CENGN transition ran into issues with SSL certificates.? We will try again Monday. Scott On 2023-07-20 15:40, Scott.Little wrote: > Final sync missed some content.? I've restarted it, but it will run > into the evening. > > We'll delay the DNS change to redirect mirror.starlingx.cengn.ca to > mirror.starlingx.windriver.com until Jul 21 13:00 UTC? (9 am Easter) > > Scott > > On 2023-07-20 09:36, Scott.Little wrote: >> >> The final CENGN master branch build successful.? Timestamp >> 20230719T142650Z. >> >> Seeing no objections, we'll start enacting the transition plan. >> >> Scott >> >> >> On 2023-07-19 10:44, Little, Scott wrote: >>> Based on the community call, the agreed plan is as follows. >>> >>> - Allow the current CENGN master branch build to complete. >>> - Freeze further build attempts on CENGN as of July 20? 04:00 UTC. >>> - Final sync of the Wind River mirror relative to the CENGN mirror >>> starts Jul 20 13:00 UTC >>> - DNS changed to redirect mirror.starlingx.cengn.ca to >>> mirror.starlingx.windriver.com Jul 20 16:00 UTC >>> - Test build(s) of StarlingX in Wind River hardware Jul 20 16:00 UTC- >>> July 21 20:00 UTC >>> - July 21 20:00 UTC... If tests are successful, start scheduled builds >>> on Wind River infrastructure, otherwise revert to CENGN as re-enable >>> scheduled builds on their side. >>> >>> If there are objections to this plan, please speak out today. >>> >>> Scott >>> >>> >>> On 2023-07-19 09:24, Little, Scott wrote: >>>> As you should all be aware by now, StarlingX will be relocating our >>>> build and mirror service away from CENGN.? The replacement host, at >>>> least for the near future, will be Wind River.? CENGN has graciously >>>> offered to redirect traffic referencing mirror.starlingx.cengn.ca >>>> to our >>>> new home at mirror.starlingx.windriver.com for an extended period to >>>> ease the transition. >>>> >>>> The Wind River infrastructure is now ready.? We need to plan a time >>>> for >>>> the transition.? During the transition, we'll need to disable >>>> builds for >>>> a day or two.? This will give us a bit of time to ensure the Wind >>>> River >>>> is fully up to date with the final CENGN content.? We will discuss the >>>> timing at this weeks community meeting.? If you have concerns, please >>>> attend. >>>> >>>> Scott Little >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From Ghada.Khalil at windriver.com Mon Jul 24 16:54:28 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Mon, 24 Jul 2023 16:54:28 +0000 Subject: [Starlingx-discuss] Launchpad status not updating automatically Message-ID: Hello all, I noticed that stx launchpads are not getting automatically updated when gerrit reviews merge even when the "Closes-Bug" is used correctly in the code review comment. At this point, I'm not sure if this issue is reported/known to the opendev infrastructure team or not. @Ildiko Vancsa can you help report this issue or let me know how to do that myself? Until the issue is resolved, please update your LPs manually: put a link to the review and mark the LP as Fix Released when it's merged. Example: https://bugs.launchpad.net/starlingx/+bug/2028302 https://bugs.launchpad.net/starlingx/+bug/2027827 Regards, Ghada -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openstack.org Mon Jul 24 18:27:46 2023 From: ildiko at openstack.org (Ildiko Vancsa) Date: Mon, 24 Jul 2023 11:27:46 -0700 Subject: [Starlingx-discuss] Launchpad status not updating automatically In-Reply-To: References: Message-ID: Hi Ghada, Thank you for raising this issue. I just did a quick check. It was reported to the OpenDev community a little while back. The suspected cause for the issue was a check that was matching the Gerrit and Launchpad project names, which for StarlingX don?t always line up. There was a fix merged for this particular issue: https://review.opendev.org/888321 The OpenDev team needs to build and upload a new Gerrit image that contains the fix, and then restart the service. They will look into scheduling that this week. Please see the logs of the related conversation in #opendev on the OFTC IRC network here: https://meetings.opendev.org/irclogs/%23opendev/%23opendev.2023-07-24.log.html#t2023-07-24T17:19:24 Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation > On Jul 24, 2023, at 09:54, Khalil, Ghada wrote: > > > Hello all, > I noticed that stx launchpads are not getting automatically updated when gerrit reviews merge even when the ?Closes-Bug? is used correctly in the code review comment. > > At this point, I?m not sure if this issue is reported/known to the opendev infrastructure team or not. at Ildiko Vancsa can you help report this issue or let me know how to do that myself? > > Until the issue is resolved, please update your LPs manually: put a link to the review and mark the LP as Fix Released when it's merged. > > Example: > https://bugs.launchpad.net/starlingx/+bug/2028302 > https://bugs.launchpad.net/starlingx/+bug/2027827 > > Regards, > Ghada > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From fungi at yuggoth.org Mon Jul 24 19:20:40 2023 From: fungi at yuggoth.org (Jeremy Stanley) Date: Mon, 24 Jul 2023 19:20:40 +0000 Subject: [Starlingx-discuss] Launchpad status not updating automatically In-Reply-To: References: Message-ID: <20230724192039.sui4ss5qxtl6zpof@yuggoth.org> On 2023-07-24 11:27:46 -0700 (-0700), Ildiko Vancsa wrote: [...] > The OpenDev team needs to build and upload a new Gerrit image that > contains the fix, and then restart the service. They will look > into scheduling that this week. [...] To be clear, the fixed image is already built and uploaded, it's just that we need to schedule some brief downtime to restart the service on the new image. However, we've also got a pending point release for Gerrit and a fix for how we're persisting Gerrit's commit replication queue, so would ideally work those in before the restart as well to minimize the number of planned outages in the near future. -- 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 scott.little at eng.windriver.com Mon Jul 24 19:56:45 2023 From: scott.little at eng.windriver.com (Scott.Little) Date: Mon, 24 Jul 2023 15:56:45 -0400 Subject: [Starlingx-discuss] Transition away from CENGN In-Reply-To: <4cd18adf-bce1-d339-a0d6-6c653d03274e@eng.windriver.com> References: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> <51e5a036-a6bb-ad55-bbdd-1fc0fb1abfe6@eng.windriver.com> <4cd18adf-bce1-d339-a0d6-6c653d03274e@eng.windriver.com> Message-ID: <4a75c184-ba44-f413-8ba4-8f19e542244f@eng.windriver.com> The transition is back in effect.? A number of issues are being worked Certificate issues - Certificates on the web server has been updated to provide the full chain of trust. - We'll be issuing updates to dockerfiles that build from an 'older' image, to update the root certificates and complete the chain of trust. The first two ... https://review.opendev.org/c/starlingx/tools/+/889365 , https://ala-codereviewti-prod.wrs.com/c/cgcs/opendev.org.starlingx.tools/+/15930 Connectivity issues. - Mostly from Brazil so far ... Reported to IT for investigation. Scott On 2023-07-24 10:49, Scott.Little wrote: > The CENGN transition ran into issues with SSL certificates.? We will > try again Monday. > > Scott > > > On 2023-07-20 15:40, Scott.Little wrote: >> Final sync missed some content.? I've restarted it, but it will run >> into the evening. >> >> We'll delay the DNS change to redirect mirror.starlingx.cengn.ca to >> mirror.starlingx.windriver.com until Jul 21 13:00 UTC? (9 am Easter) >> >> Scott >> >> On 2023-07-20 09:36, Scott.Little wrote: >>> >>> The final CENGN master branch build successful.? Timestamp >>> 20230719T142650Z. >>> >>> Seeing no objections, we'll start enacting the transition plan. >>> >>> Scott >>> >>> >>> On 2023-07-19 10:44, Little, Scott wrote: >>>> Based on the community call, the agreed plan is as follows. >>>> >>>> - Allow the current CENGN master branch build to complete. >>>> - Freeze further build attempts on CENGN as of July 20 04:00 UTC. >>>> - Final sync of the Wind River mirror relative to the CENGN mirror >>>> starts Jul 20 13:00 UTC >>>> - DNS changed to redirect mirror.starlingx.cengn.ca to >>>> mirror.starlingx.windriver.com Jul 20 16:00 UTC >>>> - Test build(s) of StarlingX in Wind River hardware Jul 20 16:00 UTC- >>>> July 21 20:00 UTC >>>> - July 21 20:00 UTC... If tests are successful, start scheduled builds >>>> on Wind River infrastructure, otherwise revert to CENGN as re-enable >>>> scheduled builds on their side. >>>> >>>> If there are objections to this plan, please speak out today. >>>> >>>> Scott >>>> >>>> >>>> On 2023-07-19 09:24, Little, Scott wrote: >>>>> As you should all be aware by now, StarlingX will be relocating our >>>>> build and mirror service away from CENGN.? The replacement host, at >>>>> least for the near future, will be Wind River.? CENGN has graciously >>>>> offered to redirect traffic referencing mirror.starlingx.cengn.ca >>>>> to our >>>>> new home at mirror.starlingx.windriver.com for an extended period to >>>>> ease the transition. >>>>> >>>>> The Wind River infrastructure is now ready.? We need to plan a >>>>> time for >>>>> the transition.? During the transition, we'll need to disable >>>>> builds for >>>>> a day or two.? This will give us a bit of time to ensure the Wind >>>>> River >>>>> is fully up to date with the final CENGN content.? We will discuss >>>>> the >>>>> timing at this weeks community meeting.? If you have concerns, please >>>>> attend. >>>>> >>>>> Scott Little >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Tue Jul 25 13:52:16 2023 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Tue, 25 Jul 2023 13:52:16 +0000 Subject: [Starlingx-discuss] Transition away from CENGN In-Reply-To: <4a75c184-ba44-f413-8ba4-8f19e542244f@eng.windriver.com> References: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> <51e5a036-a6bb-ad55-bbdd-1fc0fb1abfe6@eng.windriver.com> <4cd18adf-bce1-d339-a0d6-6c653d03274e@eng.windriver.com> <4a75c184-ba44-f413-8ba4-8f19e542244f@eng.windriver.com> Message-ID: We discovered an additional problem: the downloader script leaves corrupted files behind. Workaround: stx config --add repomgr.cengnurl "https://mirror.starlingx.windriver.com/mirror stx-init-env --docker-login LP: https://bugs.launchpad.net/starlingx/+bug/2028672 ________________________________ From: Scott.Little Sent: July 24, 2023 3:56 PM To: starlingx-discuss at lists.starlingx.io Subject: Re: [Starlingx-discuss] Transition away from CENGN The transition is back in effect. A number of issues are being worked Certificate issues - Certificates on the web server has been updated to provide the full chain of trust. - We'll be issuing updates to dockerfiles that build from an 'older' image, to update the root certificates and complete the chain of trust. The first two ... https://review.opendev.org/c/starlingx/tools/+/889365, https://ala-codereviewti-prod.wrs.com/c/cgcs/opendev.org.starlingx.tools/+/15930 Connectivity issues. - Mostly from Brazil so far ... Reported to IT for investigation. Scott On 2023-07-24 10:49, Scott.Little wrote: The CENGN transition ran into issues with SSL certificates. We will try again Monday. Scott On 2023-07-20 15:40, Scott.Little wrote: Final sync missed some content. I've restarted it, but it will run into the evening. We'll delay the DNS change to redirect mirror.starlingx.cengn.ca to http://mirror.starlingx.windriver.com until Jul 21 13:00 UTC (9 am Easter) Scott On 2023-07-20 09:36, Scott.Little wrote: The final CENGN master branch build successful. Timestamp 20230719T142650Z. Seeing no objections, we'll start enacting the transition plan. Scott On 2023-07-19 10:44, Little, Scott wrote: Based on the community call, the agreed plan is as follows. - Allow the current CENGN master branch build to complete. - Freeze further build attempts on CENGN as of July 20 04:00 UTC. - Final sync of the Wind River mirror relative to the CENGN mirror starts Jul 20 13:00 UTC - DNS changed to redirect mirror.starlingx.cengn.ca to http://mirror.starlingx.windriver.com Jul 20 16:00 UTC - Test build(s) of StarlingX in Wind River hardware Jul 20 16:00 UTC- July 21 20:00 UTC - July 21 20:00 UTC... If tests are successful, start scheduled builds on Wind River infrastructure, otherwise revert to CENGN as re-enable scheduled builds on their side. If there are objections to this plan, please speak out today. Scott On 2023-07-19 09:24, Little, Scott wrote: As you should all be aware by now, StarlingX will be relocating our build and mirror service away from CENGN. The replacement host, at least for the near future, will be Wind River. CENGN has graciously offered to redirect traffic referencing mirror.starlingx.cengn.ca to our new home at http://mirror.starlingx.windriver.com for an extended period to ease the transition. The Wind River infrastructure is now ready. We need to plan a time for the transition. During the transition, we'll need to disable builds for a day or two. This will give us a bit of time to ensure the Wind River is fully up to date with the final CENGN content. We will discuss the timing at this weeks community meeting. If you have concerns, please attend. Scott Little _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ramaswamy.Subramanian at windriver.com Tue Jul 25 13:56:52 2023 From: Ramaswamy.Subramanian at windriver.com (Subramanian, Ramaswamy) Date: Tue, 25 Jul 2023 13:56:52 +0000 Subject: [Starlingx-discuss] DistCloud/Flock Services Project Meeting Minutes Message-ID: July 25, 2023: * Below bugs are manually updated as the Launchpad / Gerrit integration needs to be fixed. Infrastructure issue are being investigated. * https://bugs.launchpad.net/starlingx/+bug/2028379 * StarlingX 9.0 Release: * Feature development in progress. More details available in the release planning spread sheet. * Stale Code Review Cleanup to keep the review queue sane (more than 1 year old with no activity) * https://review.opendev.org/c/starlingx/config/+/773303 * https://review.opendev.org/c/starlingx/config/+/812769 * Bug cleanup (more than 1 year old with no activity) * Closed. * https://bugs.launchpad.net/starlingx/+bug/1858937 * https://bugs.launchpad.net/starlingx/+bug/1852734 * https://bugs.launchpad.net/starlingx/+bug/1852729 * https://bugs.launchpad.net/starlingx/+bug/1852836 * https://bugs.launchpad.net/starlingx/+bug/1860473 * Candidate for Closure. * https://bugs.launchpad.net/starlingx/+bug/1838524 * https://bugs.launchpad.net/starlingx/+bug/1854367 * https://bugs.launchpad.net/starlingx/+bug/1863377 * https://bugs.launchpad.net/starlingx/+bug/1875426 -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at eng.windriver.com Tue Jul 25 14:58:41 2023 From: scott.little at eng.windriver.com (Scott.Little) Date: Tue, 25 Jul 2023 10:58:41 -0400 Subject: [Starlingx-discuss] Transition away from CENGN In-Reply-To: <4a75c184-ba44-f413-8ba4-8f19e542244f@eng.windriver.com> References: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> <51e5a036-a6bb-ad55-bbdd-1fc0fb1abfe6@eng.windriver.com> <4cd18adf-bce1-d339-a0d6-6c653d03274e@eng.windriver.com> <4a75c184-ba44-f413-8ba4-8f19e542244f@eng.windriver.com> Message-ID: <6efdd290-a135-9594-a67c-efc109229240@eng.windriver.com> Update Certificate issues - Updates have merged, you will need to exit and rebuild your build containers. ?? i.e.? ./stx-init-env --rebuild Connectivity issues. -? The previously reported connectivity issues appear to be an internal issue within Wind River. -? If anyone OUTSIDE of Wind River is seeing connectivity issue, please report. Download issue - The 'download' tool of the Debian build is failing. - curl doesn't follow redirects unless -L option is given, and there is a redirect from mirror.starlingx.cengn.ca to mirror.starlingx.windriver.ca. - Launchpad: https://review.opendev.org/c/starlingx/root/+/889438 - Update:https://review.opendev.org/c/starlingx/root/+/889438 On 2023-07-24 15:56, Scott.Little wrote: > The transition is back in effect.? A number of issues are being worked > > Certificate issues > > - Certificates on the web server has been updated to provide the full > chain of trust. > > - We'll be issuing updates to dockerfiles that build from an 'older' > image, to update the root certificates and complete the chain of > trust. The first two ... > > https://review.opendev.org/c/starlingx/tools/+/889365 > , > > https://ala-codereviewti-prod.wrs.com/c/cgcs/opendev.org.starlingx.tools/+/15930 > > > Connectivity issues. > > - Mostly from Brazil so far ... Reported to IT for investigation. > > Scott > > > On 2023-07-24 10:49, Scott.Little wrote: >> The CENGN transition ran into issues with SSL certificates.? We will >> try again Monday. >> >> Scott >> >> >> On 2023-07-20 15:40, Scott.Little wrote: >>> Final sync missed some content.? I've restarted it, but it will run >>> into the evening. >>> >>> We'll delay the DNS change to redirect mirror.starlingx.cengn.ca >>> >>> to http://mirror.starlingx.windriver.com until Jul 21 13:00 UTC (9 >>> am Easter) >>> >>> Scott >>> >>> On 2023-07-20 09:36, Scott.Little wrote: >>>> >>>> The final CENGN master branch build successful.? Timestamp >>>> 20230719T142650Z. >>>> >>>> Seeing no objections, we'll start enacting the transition plan. >>>> >>>> Scott >>>> >>>> >>>> On 2023-07-19 10:44, Little, Scott wrote: >>>>> Based on the community call, the agreed plan is as follows. >>>>> >>>>> - Allow the current CENGN master branch build to complete. >>>>> - Freeze further build attempts on CENGN as of July 20 04:00 UTC. >>>>> - Final sync of the Wind River mirror relative to the CENGN mirror >>>>> starts Jul 20 13:00 UTC >>>>> - DNS changed to redirect mirror.starlingx.cengn.ca >>>>> >>>>> to >>>>> http://mirror.starlingx.windriver.com Jul 20 16:00 UTC >>>>> - Test build(s) of StarlingX in Wind River hardware Jul 20 16:00 UTC- >>>>> July 21 20:00 UTC >>>>> - July 21 20:00 UTC... If tests are successful, start scheduled >>>>> builds >>>>> on Wind River infrastructure, otherwise revert to CENGN as re-enable >>>>> scheduled builds on their side. >>>>> >>>>> If there are objections to this plan, please speak out today. >>>>> >>>>> Scott >>>>> >>>>> >>>>> On 2023-07-19 09:24, Little, Scott wrote: >>>>>> As you should all be aware by now, StarlingX will be relocating our >>>>>> build and mirror service away from CENGN.? The replacement host, at >>>>>> least for the near future, will be Wind River.? CENGN has graciously >>>>>> offered to redirect traffic referencing mirror.starlingx.cengn.ca >>>>>> >>>>>> to our >>>>>> new home at http://mirror.starlingx.windriver.com for an extended >>>>>> period to >>>>>> ease the transition. >>>>>> >>>>>> The Wind River infrastructure is now ready.? We need to plan a >>>>>> time for >>>>>> the transition.? During the transition, we'll need to disable >>>>>> builds for >>>>>> a day or two.? This will give us a bit of time to ensure the Wind >>>>>> River >>>>>> is fully up to date with the final CENGN content.? We will >>>>>> discuss the >>>>>> timing at this weeks community meeting.? If you have concerns, >>>>>> please >>>>>> attend. >>>>>> >>>>>> Scott Little >>>>>> >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Davlet.Panech at windriver.com Wed Jul 26 15:03:25 2023 From: Davlet.Panech at windriver.com (Panech, Davlet) Date: Wed, 26 Jul 2023 15:03:25 +0000 Subject: [Starlingx-discuss] How to avoid DockerHub download rate limit when building StarlingX Message-ID: Good day, As DockerHub has recently changed its download rate restrictions policy, you may have experienced errors while building StarlingX, similar to: "You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit" While the build team is pondering a permanent solution, there are a few steps you can take that *may* alleviate this problem, depending on the network configuration of your build environment: * Register an account with Docker Hub * Use the "--dockerhub-login" command-line option when calling "stx-init-env" to start the build environment (new option that merged recently) * Use "docker login" inside the build container before building app containers Hope this helps, D. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Wed Jul 26 19:10:26 2023 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Wed, 26 Jul 2023 21:10:26 +0200 Subject: [Starlingx-discuss] How to avoid DockerHub download rate limit when building StarlingX In-Reply-To: References: Message-ID: <861ED82C-C400-43C2-9C31-0C46C6D2E6CB@gmail.com> Hi, Thanks Davlet for sharing a workaround. I also asked about alternatives in the #opendev channel. The team hasn?t done an extensive research before deciding with Quay.io. They were considering that service or hosting a registry themselves. The Zuul community already migrated over to Quay, while OpenDev still has some dependencies on Docker that causes delays. I was also pointed at the Sovereign Cloud Stack community, who hosts their own registry, based on Harbor, which is an open source tool: https://sovereigncloudstack.github.io/website/tech/2023/05/30/registry-migration-upgrade/ You can find the entire conversation here: https://meetings.opendev.org/irclogs/%23opendev/%23opendev.2023-07-26.log.html#t2023-07-26T15:45:40 In summary, the following alternatives came up so far: - Quay - https://quay.io - Harbor - https://goharbor.io - Nexus Repository - https://www.sonatype.com/products/sonatype-nexus-repository I hope this helps. Best Regards, Ildik? > On Jul 26, 2023, at 17:03, Panech, Davlet wrote: > > Good day, > > As DockerHub has recently changed its download rate restrictions policy, you may have experienced errors while building StarlingX, similar to: > > "You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit" > > While the build team is pondering a permanent solution, there are a few steps you can take that *may* alleviate this problem, depending on the network configuration of your build environment: > ? Register an account with Docker Hub > ? Use the "--dockerhub-login" command-line option when calling "stx-init-env" to start the build environment (new option that merged recently) > ? Use "docker login" inside the build container before building app containers > Hope this helps, > D. > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io From Trevor.Tao at arm.com Thu Jul 27 09:06:01 2023 From: Trevor.Tao at arm.com (Trevor Tao) Date: Thu, 27 Jul 2023 09:06:01 +0000 Subject: [Starlingx-discuss] StarlingX CI/CD setup on Arm platform Message-ID: Hi Steve, StarlingX: From the OS distro meeting yesterday, we knew that there would be 6 Arm servers contributed to our community to do the CI/CD related work. So we would like to ask who can help on the setup of CI/CD environment on the arm platform, and any other useful information/details for the CI/CD issue here. Thanks, Best Regards, Zijin Tao(Trevor Tao, ???) ARM Electronic Technology (Shanghai) Co., Ltd ?????????????? Building 11, Shanghai Busininess Park? , No.1016 Tianlin Rd, Minhang District, Shanghai, 200233 China ?????????1016???????2??10??200233 Cell: +86-153 7109 6192 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Thu Jul 27 09:20:34 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Thu, 27 Jul 2023 11:20:34 +0200 Subject: [Starlingx-discuss] StarlingX Matrix next steps and room structure Message-ID: <5B2F3840-4294-42A5-8E26-413DFF23DEA4@openinfra.dev> Hi StarlingX Community, I?m reaching out with updates about using Matrix as a community chat tool onwards. With support from the StarlingX TSC and contributors, and no objections raised, the community decided to move over to Matrix from IRC! Next steps: - Once the community agrees on a room structure, I will go ahead to create that on the Matrix instance that the OpenDev community is maintaining - As the #starlingX IRC channel is available through a bridge on Matrix, the channel will still be available to provide a grace period - I will update the references to the chat platform on the website and other community resources Proposed room structure: - General discussions: starlingx-general - Project team channels: * starlingx-build * starlingx-containers * starlingx-distcloud * starlingx-distro * starlingx-docs * starlingx-flock * starlingx-networking * starlingx-openstack * starlingx-release * starlingx-security * starlingx-test Does the above room setup work for the community? __Please share your questions and concerns by end of day on next Tuesday (August 1).__ Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation From fungi at yuggoth.org Thu Jul 27 11:53:20 2023 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 27 Jul 2023 11:53:20 +0000 Subject: [Starlingx-discuss] Launchpad status not updating automatically In-Reply-To: <20230724192039.sui4ss5qxtl6zpof@yuggoth.org> References: <20230724192039.sui4ss5qxtl6zpof@yuggoth.org> Message-ID: <20230727115319.2baxubtximmalx64@yuggoth.org> On 2023-07-24 19:20:40 +0000 (+0000), Jeremy Stanley wrote: [...] > we need to schedule some brief downtime to restart the service on > the new image. [...] We restarted Gerrit yesterday for a version upgrade, which also resulted in the fix for the bug updating hook script taking effect. Any changes merged after 2023-07-26 21:05 UTC should close corresponding bugtasks in Launchpad as expected. Changes which merged prior to that, since about 2023-05-12 when the service was originally restarted onto the broken hook script change, may need their bugtasks manually set to fix committed or fix released. -- 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 douglas.pereira at encora.com Thu Jul 27 13:25:49 2023 From: douglas.pereira at encora.com (Douglas Lopes Pereira) Date: Thu, 27 Jul 2023 13:25:49 +0000 Subject: [Starlingx-discuss] StarlingX Matrix next steps and room structure In-Reply-To: <5B2F3840-4294-42A5-8E26-413DFF23DEA4@openinfra.dev> References: <5B2F3840-4294-42A5-8E26-413DFF23DEA4@openinfra.dev> Message-ID: +1 Douglas Lopes Pereira Software Development Manager M: +55 (19) 99212-3212 Campinas, BR [Encora] [We are proud to be recognized as Leaders in digital engineering services by Zinnov zones] ________________________________ From: Ildiko Vancsa Sent: Thursday, July 27, 2023 6:20 AM To: StarlingX ML Subject: [Starlingx-discuss] StarlingX Matrix next steps and room structure External Mail: Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I?m reaching out with updates about using Matrix as a community chat tool onwards. With support from the StarlingX TSC and contributors, and no objections raised, the community decided to move over to Matrix from IRC! Next steps: - Once the community agrees on a room structure, I will go ahead to create that on the Matrix instance that the OpenDev community is maintaining - As the #starlingX IRC channel is available through a bridge on Matrix, the channel will still be available to provide a grace period - I will update the references to the chat platform on the website and other community resources Proposed room structure: - General discussions: starlingx-general - Project team channels: * starlingx-build * starlingx-containers * starlingx-distcloud * starlingx-distro * starlingx-docs * starlingx-flock * starlingx-networking * starlingx-openstack * starlingx-release * starlingx-security * starlingx-test Does the above room setup work for the community? __Please share your questions and concerns by end of day on next Tuesday (August 1).__ Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at eng.windriver.com Thu Jul 27 13:43:13 2023 From: scott.little at eng.windriver.com (Scott.Little) Date: Thu, 27 Jul 2023 09:43:13 -0400 Subject: [Starlingx-discuss] Transition away from CENGN In-Reply-To: <6efdd290-a135-9594-a67c-efc109229240@eng.windriver.com> References: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> <51e5a036-a6bb-ad55-bbdd-1fc0fb1abfe6@eng.windriver.com> <4cd18adf-bce1-d339-a0d6-6c653d03274e@eng.windriver.com> <4a75c184-ba44-f413-8ba4-8f19e542244f@eng.windriver.com> <6efdd290-a135-9594-a67c-efc109229240@eng.windriver.com> Message-ID: <3fba09f6-7960-a222-7af7-fe0c29b7485a@eng.windriver.com> Update We have a successful StarlingX master branch build!? Fresh containers are included. https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230726T235341Z/outputs/ A fresh set of build containers have also been published.? So you don't have to rebuild them yourself, but a 'nuke' is required to force download of the latest build containers. ??? ./stx-init-env --nuke ??? ./stx-init-env One additional update was required to update certificates and allow apt to use https from within our Debian sbuild chroot. https://review.opendev.org/c/starlingx/tools/+/889783 After a 'repo sync' and 'download', your next build-pkgs should include the '--refresh_chroots' arguement ??? build-pkgs --refresh_chroots I'll back port the changes to r/stx.8.0 starting this morning Scott On 2023-07-25 10:58, Scott.Little wrote: > Update > > Certificate issues > > - Updates have merged, you will need to exit and rebuild your build > containers. > ?? i.e.? ./stx-init-env --rebuild > > Connectivity issues. > > -? The previously reported connectivity issues appear to be an > internal issue within Wind River. > -? If anyone OUTSIDE of Wind River is seeing connectivity issue, > please report. > > Download issue > > - The 'download' tool of the Debian build is failing. > - curl doesn't follow redirects unless -L option is given, and there > is a redirect from mirror.starlingx.cengn.ca > > to mirror.starlingx.windriver.ca. > - Launchpad: https://review.opendev.org/c/starlingx/root/+/889438 > - Update:https://review.opendev.org/c/starlingx/root/+/889438 > > > > > > > > On 2023-07-24 15:56, Scott.Little wrote: >> The transition is back in effect. A number of issues are being worked >> >> Certificate issues >> >> - Certificates on the web server has been updated to provide the full >> chain of trust. >> >> - We'll be issuing updates to dockerfiles that build from an 'older' >> image, to update the root certificates and complete the chain of >> trust. The first two ... >> >> https://review.opendev.org/c/starlingx/tools/+/889365 >> , >> >> https://ala-codereviewti-prod.wrs.com/c/cgcs/opendev.org.starlingx.tools/+/15930 >> >> >> Connectivity issues. >> >> - Mostly from Brazil so far ... Reported to IT for investigation. >> >> Scott >> >> >> On 2023-07-24 10:49, Scott.Little wrote: >>> The CENGN transition ran into issues with SSL certificates.? We will >>> try again Monday. >>> >>> Scott >>> >>> >>> On 2023-07-20 15:40, Scott.Little wrote: >>>> Final sync missed some content.? I've restarted it, but it will run >>>> into the evening. >>>> >>>> We'll delay the DNS change to redirect mirror.starlingx.cengn.ca >>>> >>>> to http://mirror.starlingx.windriver.com until Jul 21 13:00 UTC? (9 >>>> am Easter) >>>> >>>> Scott >>>> >>>> On 2023-07-20 09:36, Scott.Little wrote: >>>>> >>>>> The final CENGN master branch build successful.? Timestamp >>>>> 20230719T142650Z. >>>>> >>>>> Seeing no objections, we'll start enacting the transition plan. >>>>> >>>>> Scott >>>>> >>>>> >>>>> On 2023-07-19 10:44, Little, Scott wrote: >>>>>> Based on the community call, the agreed plan is as follows. >>>>>> >>>>>> - Allow the current CENGN master branch build to complete. >>>>>> - Freeze further build attempts on CENGN as of July 20 04:00 UTC. >>>>>> - Final sync of the Wind River mirror relative to the CENGN mirror >>>>>> starts Jul 20 13:00 UTC >>>>>> - DNS changed to redirect mirror.starlingx.cengn.ca >>>>>> >>>>>> to >>>>>> http://mirror.starlingx.windriver.com Jul 20 16:00 UTC >>>>>> - Test build(s) of StarlingX in Wind River hardware Jul 20 16:00 >>>>>> UTC- >>>>>> July 21 20:00 UTC >>>>>> - July 21 20:00 UTC... If tests are successful, start scheduled >>>>>> builds >>>>>> on Wind River infrastructure, otherwise revert to CENGN as re-enable >>>>>> scheduled builds on their side. >>>>>> >>>>>> If there are objections to this plan, please speak out today. >>>>>> >>>>>> Scott >>>>>> >>>>>> >>>>>> On 2023-07-19 09:24, Little, Scott wrote: >>>>>>> As you should all be aware by now, StarlingX will be relocating our >>>>>>> build and mirror service away from CENGN.? The replacement host, at >>>>>>> least for the near future, will be Wind River.? CENGN has >>>>>>> graciously >>>>>>> offered to redirect traffic referencing >>>>>>> mirror.starlingx.cengn.ca >>>>>>> >>>>>>> to our >>>>>>> new home at http://mirror.starlingx.windriver.com for an >>>>>>> extended period to >>>>>>> ease the transition. >>>>>>> >>>>>>> The Wind River infrastructure is now ready.? We need to plan a >>>>>>> time for >>>>>>> the transition.? During the transition, we'll need to disable >>>>>>> builds for >>>>>>> a day or two.? This will give us a bit of time to ensure the >>>>>>> Wind River >>>>>>> is fully up to date with the final CENGN content.? We will >>>>>>> discuss the >>>>>>> timing at this weeks community meeting.? If you have concerns, >>>>>>> please >>>>>>> attend. >>>>>>> >>>>>>> Scott Little >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Starlingx-discuss mailing list >>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>> >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Peng.Peng at windriver.com Tue Jul 25 18:54:48 2023 From: Peng.Peng at windriver.com (Peng, Peng) Date: Tue, 25 Jul 2023 18:54:48 +0000 Subject: [Starlingx-discuss] StarlingX sanity is not available this week. Message-ID: Hi, Due to lab issue, Sanity was not able to run this week. We will resume next week. Regards, PV team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Rob.Cooke at windriver.com Tue Jul 25 19:02:21 2023 From: Rob.Cooke at windriver.com (Cooke, Rob) Date: Tue, 25 Jul 2023 19:02:21 +0000 Subject: [Starlingx-discuss] Minutes: Test Status Call - July 25, 2023 Message-ID: Hi everyone, Please find below the minutes from this week's StarlingX Test Status Call: Minutes for 07/25/2023 * Open Topics: ? Planned to discuss the feature list for STX9.0 in the release call last week. * Is there a plan to revisit the list, are all items still planned for STX9.0, does the list need refinement etc. * The Release call was canceled, will discuss the topic at the next release call * Sanity Status: o Sanity on STX 9.0 - Not Executed ? Issues getting the software installed has prevented execution of sanity this week ? Last execution, July 17, 2023 - Results email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014295.html o Sanity on STX 9.0 plus Openstack - Not executed ? Similar issues getting the software installed has prevented execution of sanity this week ? Both teams are working on identifying the issues to enable sanity execution ? Last execution, July 17, 2023 - Results email: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014296.html * Feature Test Status: o Feature testing is tracked in the following google sheet: ? https://docs.google.com/spreadsheets/d/1El3g0ute5K2S5DTR9p_rxa1jQlq8gcUzgMCNCE_sx8g/edit#gid=968103774 ? Some features are in progress, sheet does need updating ACTION: Rob/Nimalini * Regression Testing will be tracked here closer to release end: ? https://docs.google.com/spreadsheets/d/1NjYk9N0whK91nHViB5HFG2C1-XdJ09StVuLMxsz0KAY/edit?pli=1#gid=1717644237 Thanks, Rob -------------- next part -------------- An HTML attachment was scrubbed... URL: From scott.little at windriver.com Thu Jul 27 13:40:02 2023 From: scott.little at windriver.com (Scott Little) Date: Thu, 27 Jul 2023 09:40:02 -0400 Subject: [Starlingx-discuss] Transition away from CENGN In-Reply-To: <6efdd290-a135-9594-a67c-efc109229240@eng.windriver.com> References: <41da6c34-9f7b-e77b-8ba5-400bbf14e3d6@eng.windriver.com> <51e5a036-a6bb-ad55-bbdd-1fc0fb1abfe6@eng.windriver.com> <4cd18adf-bce1-d339-a0d6-6c653d03274e@eng.windriver.com> <4a75c184-ba44-f413-8ba4-8f19e542244f@eng.windriver.com> <6efdd290-a135-9594-a67c-efc109229240@eng.windriver.com> Message-ID: Update We have a successful StarlingX master branch build!? Fresh containers are included. https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic/20230726T235341Z/outputs/ A fresh set of build containers have also been published.? So you don't have to rebuild them yourself, but a 'nuke' is required to force download of the latest build containers. ??? ./stx-init-env --nuke ??? ./stx-init-env One additional update was required to update certificates and allow apt to use https from within our Debian sbuild chroot. https://review.opendev.org/c/starlingx/tools/+/889783 After a 'repo sync' and 'download', your next build-pkgs should include the '--refresh_chroots' arguement ??? build-pkgs --refresh_chroots I'll back port the changes to r/stx.8.0 starting this morning Scott On 2023-07-25 10:58, Scott.Little wrote: > Update > > Certificate issues > > - Updates have merged, you will need to exit and rebuild your build > containers. > ?? i.e.? ./stx-init-env --rebuild > > Connectivity issues. > > -? The previously reported connectivity issues appear to be an > internal issue within Wind River. > -? If anyone OUTSIDE of Wind River is seeing connectivity issue, > please report. > > Download issue > > - The 'download' tool of the Debian build is failing. > - curl doesn't follow redirects unless -L option is given, and there > is a redirect from mirror.starlingx.cengn.ca > > to mirror.starlingx.windriver.ca. > - Launchpad: https://review.opendev.org/c/starlingx/root/+/889438 > - Update:https://review.opendev.org/c/starlingx/root/+/889438 > > > > > > > > On 2023-07-24 15:56, Scott.Little wrote: >> The transition is back in effect. A number of issues are being worked >> >> Certificate issues >> >> - Certificates on the web server has been updated to provide the full >> chain of trust. >> >> - We'll be issuing updates to dockerfiles that build from an 'older' >> image, to update the root certificates and complete the chain of >> trust. The first two ... >> >> https://review.opendev.org/c/starlingx/tools/+/889365 >> , >> >> https://ala-codereviewti-prod.wrs.com/c/cgcs/opendev.org.starlingx.tools/+/15930 >> >> >> Connectivity issues. >> >> - Mostly from Brazil so far ... Reported to IT for investigation. >> >> Scott >> >> >> On 2023-07-24 10:49, Scott.Little wrote: >>> The CENGN transition ran into issues with SSL certificates.? We will >>> try again Monday. >>> >>> Scott >>> >>> >>> On 2023-07-20 15:40, Scott.Little wrote: >>>> Final sync missed some content.? I've restarted it, but it will run >>>> into the evening. >>>> >>>> We'll delay the DNS change to redirect mirror.starlingx.cengn.ca >>>> >>>> to http://mirror.starlingx.windriver.com until Jul 21 13:00 UTC? (9 >>>> am Easter) >>>> >>>> Scott >>>> >>>> On 2023-07-20 09:36, Scott.Little wrote: >>>>> >>>>> The final CENGN master branch build successful.? Timestamp >>>>> 20230719T142650Z. >>>>> >>>>> Seeing no objections, we'll start enacting the transition plan. >>>>> >>>>> Scott >>>>> >>>>> >>>>> On 2023-07-19 10:44, Little, Scott wrote: >>>>>> Based on the community call, the agreed plan is as follows. >>>>>> >>>>>> - Allow the current CENGN master branch build to complete. >>>>>> - Freeze further build attempts on CENGN as of July 20 04:00 UTC. >>>>>> - Final sync of the Wind River mirror relative to the CENGN mirror >>>>>> starts Jul 20 13:00 UTC >>>>>> - DNS changed to redirect mirror.starlingx.cengn.ca >>>>>> >>>>>> to >>>>>> http://mirror.starlingx.windriver.com Jul 20 16:00 UTC >>>>>> - Test build(s) of StarlingX in Wind River hardware Jul 20 16:00 >>>>>> UTC- >>>>>> July 21 20:00 UTC >>>>>> - July 21 20:00 UTC... If tests are successful, start scheduled >>>>>> builds >>>>>> on Wind River infrastructure, otherwise revert to CENGN as re-enable >>>>>> scheduled builds on their side. >>>>>> >>>>>> If there are objections to this plan, please speak out today. >>>>>> >>>>>> Scott >>>>>> >>>>>> >>>>>> On 2023-07-19 09:24, Little, Scott wrote: >>>>>>> As you should all be aware by now, StarlingX will be relocating our >>>>>>> build and mirror service away from CENGN.? The replacement host, at >>>>>>> least for the near future, will be Wind River.? CENGN has >>>>>>> graciously >>>>>>> offered to redirect traffic referencing >>>>>>> mirror.starlingx.cengn.ca >>>>>>> >>>>>>> to our >>>>>>> new home at http://mirror.starlingx.windriver.com for an >>>>>>> extended period to >>>>>>> ease the transition. >>>>>>> >>>>>>> The Wind River infrastructure is now ready.? We need to plan a >>>>>>> time for >>>>>>> the transition.? During the transition, we'll need to disable >>>>>>> builds for >>>>>>> a day or two.? This will give us a bit of time to ensure the >>>>>>> Wind River >>>>>>> is fully up to date with the final CENGN content.? We will >>>>>>> discuss the >>>>>>> timing at this weeks community meeting.? If you have concerns, >>>>>>> please >>>>>>> attend. >>>>>>> >>>>>>> Scott Little >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Starlingx-discuss mailing list >>>>>>> Starlingx-discuss at lists.starlingx.io >>>>>> >>>>>> _______________________________________________ >>>>>> Starlingx-discuss mailing list >>>>>> Starlingx-discuss at lists.starlingx.io >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Starlingx-discuss mailing list >>>>> Starlingx-discuss at lists.starlingx.io >>>> >>>> >>>> >>>> _______________________________________________ >>>> Starlingx-discuss mailing list >>>> Starlingx-discuss at lists.starlingx.io >>> >>> >>> >>> _______________________________________________ >>> Starlingx-discuss mailing list >>> Starlingx-discuss at lists.starlingx.io >> >> >> >> _______________________________________________ >> Starlingx-discuss mailing list >> Starlingx-discuss at lists.starlingx.io > > > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Gabriel.CalixtodePaula at windriver.com Thu Jul 27 14:35:36 2023 From: Gabriel.CalixtodePaula at windriver.com (Calixto de Paula, Gabriel) Date: Thu, 27 Jul 2023 14:35:36 +0000 Subject: [Starlingx-discuss] STX + STX-Openstack MASTER sanity results not available for this week(Jul-24) Message-ID: Hi everyone. As pointed out by Rob's minutes and Peng's report , the stx-openstack sanity was not executed this week due to issues during the installation process. We are keeping an eye on how to solve this and will resume with a new sanity run on the next week. Regards. STX-Openstack Distro Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From Hugo.Brito at encora.com Thu Jul 27 14:43:37 2023 From: Hugo.Brito at encora.com (Hugo Nicodemos Andrade de Brito) Date: Thu, 27 Jul 2023 14:43:37 +0000 Subject: [Starlingx-discuss] StarlingX Matrix next steps and room structure In-Reply-To: <5B2F3840-4294-42A5-8E26-413DFF23DEA4@openinfra.dev> References: <5B2F3840-4294-42A5-8E26-413DFF23DEA4@openinfra.dev> Message-ID: +1. Are we going to have the gerrit report on each of the channels, or are we going to stop using #starlingx-gerrit? Regards, Hugo Brito (He/His) System Developer Specialist Recife, BR [Encora] [We are proud to be recognized as Leaders in digital engineering services by Zinnov zones] ________________________________ From: Ildiko Vancsa Sent: Thursday, July 27, 2023 6:20 AM To: StarlingX ML Subject: [Starlingx-discuss] StarlingX Matrix next steps and room structure External Mail: Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I?m reaching out with updates about using Matrix as a community chat tool onwards. With support from the StarlingX TSC and contributors, and no objections raised, the community decided to move over to Matrix from IRC! Next steps: - Once the community agrees on a room structure, I will go ahead to create that on the Matrix instance that the OpenDev community is maintaining - As the #starlingX IRC channel is available through a bridge on Matrix, the channel will still be available to provide a grace period - I will update the references to the chat platform on the website and other community resources Proposed room structure: - General discussions: starlingx-general - Project team channels: * starlingx-build * starlingx-containers * starlingx-distcloud * starlingx-distro * starlingx-docs * starlingx-flock * starlingx-networking * starlingx-openstack * starlingx-release * starlingx-security * starlingx-test Does the above room setup work for the community? __Please share your questions and concerns by end of day on next Tuesday (August 1).__ Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Thu Jul 27 14:49:07 2023 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 27 Jul 2023 14:49:07 +0000 Subject: [Starlingx-discuss] StarlingX Matrix next steps and room structure In-Reply-To: References: <5B2F3840-4294-42A5-8E26-413DFF23DEA4@openinfra.dev> Message-ID: <20230727144907.jehdzrrzncivpa7m@yuggoth.org> On 2023-07-27 14:43:37 +0000 (+0000), Hugo Nicodemos Andrade de Brito wrote: > +1. Are we going to have the gerrit report on each of the > channels, or are we going to stop using #starlingx-gerrit? [...] While not a direct answer to your question, we do have an equivalent of that IRC bot for Matrix, so I'm happy to help point folks to where to add configuration to get it to report in whatever Matrix channel(s) you like. Matrix has more explicit support for bot notifications, making it easier to treat them differently in your client and ignore them or have them be less intrusive in discussions, so you may not need to put them in a separate channel (but still can if you prefer). -- 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 LuanNunes.Utimura at windriver.com Thu Jul 27 15:00:13 2023 From: LuanNunes.Utimura at windriver.com (Utimura, Luan Nunes) Date: Thu, 27 Jul 2023 15:00:13 +0000 Subject: [Starlingx-discuss] StarlingX Matrix next steps and room structure In-Reply-To: <5B2F3840-4294-42A5-8E26-413DFF23DEA4@openinfra.dev> References: <5B2F3840-4294-42A5-8E26-413DFF23DEA4@openinfra.dev> Message-ID: +1 ________________________________ From: Ildiko Vancsa Sent: Thursday, July 27, 2023 6:20 AM To: StarlingX ML Subject: [Starlingx-discuss] StarlingX Matrix next steps and room structure CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I?m reaching out with updates about using Matrix as a community chat tool onwards. With support from the StarlingX TSC and contributors, and no objections raised, the community decided to move over to Matrix from IRC! Next steps: - Once the community agrees on a room structure, I will go ahead to create that on the Matrix instance that the OpenDev community is maintaining - As the #starlingX IRC channel is available through a bridge on Matrix, the channel will still be available to provide a grace period - I will update the references to the chat platform on the website and other community resources Proposed room structure: - General discussions: starlingx-general - Project team channels: * starlingx-build * starlingx-containers * starlingx-distcloud * starlingx-distro * starlingx-docs * starlingx-flock * starlingx-networking * starlingx-openstack * starlingx-release * starlingx-security * starlingx-test Does the above room setup work for the community? __Please share your questions and concerns by end of day on next Tuesday (August 1).__ Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From ThalesElero.Cervi at windriver.com Thu Jul 27 16:29:40 2023 From: ThalesElero.Cervi at windriver.com (Cervi, Thales Elero) Date: Thu, 27 Jul 2023 16:29:40 +0000 Subject: [Starlingx-discuss] StarlingX Matrix next steps and room structure In-Reply-To: <5B2F3840-4294-42A5-8E26-413DFF23DEA4@openinfra.dev> References: <5B2F3840-4294-42A5-8E26-413DFF23DEA4@openinfra.dev> Message-ID: +1 -- Thales Elero Cervi ________________________________ From: Ildiko Vancsa Sent: Thursday, July 27, 2023 6:20 AM To: StarlingX ML Subject: [Starlingx-discuss] StarlingX Matrix next steps and room structure CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I?m reaching out with updates about using Matrix as a community chat tool onwards. With support from the StarlingX TSC and contributors, and no objections raised, the community decided to move over to Matrix from IRC! Next steps: - Once the community agrees on a room structure, I will go ahead to create that on the Matrix instance that the OpenDev community is maintaining - As the #starlingX IRC channel is available through a bridge on Matrix, the channel will still be available to provide a grace period - I will update the references to the chat platform on the website and other community resources Proposed room structure: - General discussions: starlingx-general - Project team channels: * starlingx-build * starlingx-containers * starlingx-distcloud * starlingx-distro * starlingx-docs * starlingx-flock * starlingx-networking * starlingx-openstack * starlingx-release * starlingx-security * starlingx-test Does the above room setup work for the community? __Please share your questions and concerns by end of day on next Tuesday (August 1).__ Thanks and Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss at lists.starlingx.io -------------- next part -------------- An HTML attachment was scrubbed... URL: From Ghada.Khalil at windriver.com Sun Jul 30 20:42:53 2023 From: Ghada.Khalil at windriver.com (Khalil, Ghada) Date: Sun, 30 Jul 2023 20:42:53 +0000 Subject: [Starlingx-discuss] Minutes: Community Call (Jul 26, 2023) Message-ID: Etherpad: https://etherpad.opendev.org/p/stx-status Minutes from the community call July 26, 2023 Standing topics - Build - Main Branch Debian Builds - Failing due to CENGN transition - Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/ - stx.6.0 Weekly RC Builds - Failing due to CENGN transition - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/6.0/ - stx.7.0 Weekly RC Builds - Failing due to CENGN transition - Build Output: http://mirror.starlingx.cengn.ca/mirror/starlingx/rc/7.0/ - Note: No container image builds are done for stx.7.0 - stx.8.0 Weekly RC Builds - Failing due to CENGN transition - Build Output: https://mirror.starlingx.cengn.ca/mirror/starlingx/rc/8.0/ - Transition from CENGN - Build team is working on transitioning the builds to WR infrastructure as CENGN will no longer be able to host the StarlingX builds. - Timing: Tentatively end-July / early-Aug - Status: - Currently in progress - The mirror jobs and build containers are now successful - Still working through issues related to the build itself - currently focused on the ISO, then need to go to the container builds - A lot of the failures appear related to root keys which were updated with the transition - Others are related to curl not supporting dns redirect by default - Build team may need to pull on community members for their expertise to address specific issues - Sanity - Debian Main Branch Platform Sanity - Last sanity email sent on July 18: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014295.html - Status: Green for SX and DX - No new sanity since last week; attempted sanity with July 19 build (last successful build), but hit issues that are under investigation; maybe env - Debian Main Branch stx-openstack Sanity - Last sanity email sent on July 18: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014296.html - Status: RED - TX-Openstack apply failed on the openvswitch helm release. Launchpad: https://bugs.launchpad.net/starlingx/+bug/2028061 - Fix merged on July 19 - No new sanity since last week; attempted sanity with July 19 build (last successful build), but hit issues that are under investigation; maybe env - Gerrit Reviews in Need of Attention - No Gerrit reviews needing discussion 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 - Launchpad status on automatically being updated -- Ghada Khalil - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014331.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014332.html - Please check your LPs and update the status manually (Fix Released) - including a link to the review - until the fix is rolled out - Fix should be rolled out soon, but we don't have a definitive timeline from the open-infra team - File Drop Utility on CENGN - used for large log files -- Scott Little - This was implemented by a coop, but stopped working 3 years ago (~2021) - This is now impacted by the CENGN transition. - Given there have been no complaints about this tool not working in 3 years, the community agreed that it is not needed. - dockerhub is cracking down on download limits -- Scott Little - This caused a number of builds to fail - Confirmed that the StarlingX open-source status is active - However, it appears that there is still a limit being applied (incorrectly) - 100 images every 6 hours -- dockerhub supporters are not clear why this is happening - Davlet introduced an option to workaround this issue by having individual users login instead of using the same corporate IP - Action: Davlet to share this info on the mailing list and also open a stx.docs launchpad to add this info permanently to the project docs - Another suggestion is to look at an alternative to dockerhub - Examples: quay.io / nexsus-repo community edition / harbour - https://quay.io - From Ildiko: some open-infra projects moved to quay due to the dockerhub limits. Perhaps we can get some input from them. - https://www.sonatype.com/products/sonatype-nexus-repository - This would have to be handled as a feature propsal / spec given the large scope - Work would be required by the Build team - Note: StarlingX uses open-source images as well which are hosted in dockerhub - ARs from Previous Meetings - Contributing ostree package management system to the debian community - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014299.html - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014311.html - Action: Greg Waines to follow up to ensure this content can be contributed to the Debian community. - Status: Closed. Greg followed up with Chuck Short (the developer working on this) and confirmed that the intent is to socialize and contribute this content to the Debian community. - Manifest repo re-configuration / split to allow stx-openstack to be built independently from the platform - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014206.html - No concerns from the community regarding this proposal. - The key issue is scheduling time for the build team to implement the change. - Action: Build team to propose a timeline based on their priorities/availability. - Status - No update. Build team is focused on CENGN transition - StoryBoard tracking the work: https://storyboard.openstack.org/#!/story/2010797 - Renaming App Repos to remove the "armada" - https://lists.starlingx.io/pipermail/starlingx-discuss/2023-June/014215.html - Minor / cosmetic change. Lower priority, but would be nice to do. Should have no impact on runtime. - Action: Build team to propose a timeline based on their priorities/availability. (lower priority than the manifest repo re-config) - Status - No update. Build team is focused on CENGN transition - Will likely only be planned after splitting manifests for openstack - ARM Support - Action: Scott Kamp to respond to Jackie/the mailing list to provide assistance/access to some arm machines - Action: Scott Little to respond regarding build questions - Cannot mirror more files on CENGN; will need to wait until we transition away from CENGN - Action: Scott Kamp to explore providing a hosting env temporarily - No plan to publish images to dockerhub/starlingx until they are part of the official build infrastructure - Under discussion in the OS subproject meeting - Jackie is donating hardware, but it needs to be managed by someone - Status: Open ** will not explicitly be tracked here moving forward ** - This is being tracked by the TSC; so we don't need to track it in the community call as well. Open Requests for Help - Help w/ Install - Two people asking for help with installation on IRC - Bruno is trying to help them, but it appears that they are in a different timezone. If others can participate, it would be great. - Status: Open - Discussion is continuing between Bruno and others on IRC - The questions are a mix of how to setup a virtual env as well the installation itself - For virtual env, there are two options currently: vbox & libvirt/kvm - Note: There is recent effort to get libvirt/kvm working. Email reference: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-July/014267.html - Issue w/ pxebooting a second node on StarlingX - Question raised on the community call (Apr 26) by Kevin - The initial node installs/boots correctly, but but an identical second node doesn't. This setup is using vmare to run StarlingX in VMs. - Status: Open / Greg has some information to share, but isn't sure how to get in touch w/ Kevin - July 26: Agreed to remove due to lack of updates - Build System Setup - Question was posted on IRC by Kevin - StarlingX documentation has a lot of outdated information. It took a lot of digging to find the right documentation for setting up a build env with minikube. - Requested that Kevin open an LP to the doc team and/or send an email to the mailing list w/ more details to the mailing list - Status: Open / No email sent to the mailing list yet. Unsure if LP was opened. - July 26: Agreed to remove due to lack of updates - Support for StarlingX 8 setup bring up - Reported by Prashanthi - Email thread: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/014026.html - Status: - Open / Discussion is active on the mailing list. Greg providing assistance. The issues are related to date/time issues on servers being setup as well as firewall issues - CURRENTLY PAUSED ... Prashanthi had higher internal priorities that have taken her away from looking at StarlingX for the time being; waiting for Prashanthi to get back to us. - July 26: Agreed to remove due to lack of updates From ElisamaraAoki.Goncalves at windriver.com Mon Jul 31 04:07:26 2023 From: ElisamaraAoki.Goncalves at windriver.com (Goncalves, Elisamara Aoki) Date: Mon, 31 Jul 2023 04:07:26 +0000 Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 28-07-2023 Message-ID: Hello All, Here are this week?s doc team meeting minutes. Details in [2]. Join us if you have interest in StarlingX docs! We meet on Fridays 6:00 a.m. PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation Thanks, Elisamara Aoki Gon?alves ======= 28 July-23 Status: - Stx 9.0 Release Tracking Spreadsheet: Doc Stories are tracked in https://docs.google.com/spreadsheets/d/1aTjYzUkExodfayt-rjTv466jE-DP8b_YjrTHhXW6G9w/edit?usp=sharing. - To add stories that are planned for Stx 9.0 - AR Juanita - WIP - Update the "Install StarlingX Kuberbetes in a virtual environment" docs; https://docs.starlingx.io/r/stx.8.0/deploy_install_guides/release/index-install-r7-8966076f0e81.html - Greg to create a LP bug - DONE ; https://bugs.launchpad.net/starlingx/+bug/2028272 : Bugs : StarlingX (launchpad.net) - Discussion about Merging the Installation Guides ; Virtual env with the Bare metal docs. - Split the docs and retain them as separate guides at a high level. Resue content from Bare Metal in the Virtual env docs. - Opensource Project versions - Add Opensource Project versions in the Stx 9.0 RN - AR Juanita - Create a story to track and update. Gerrit reviews: - Open Reviews pending; https://review.opendev.org/q/starlingx/docs+status:open - To be reviewed and merged Launchpad Doc Bugs: - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.docs Total 10 outstanding bugs - The DOC team to create LP defects corresponding with any DS defects - WIP. Teams to add all the impacted Releases when raising a LP bug Miscellaneous Updates: - Manju asked how much HW is required including add-ons, nvidia etc. for a small organization - AR Ron - We have a fault that is preventing LPs from closing when the coorsponding Gerrit WFs. Ron spoke with Jeremy Stanley, who reproduced the bug and is investigating.CONFIRMATION PENDING - Ron to update the Verified H/W page with the automated script updates https://www.windriver.com/studio/operator/self-validated-and-certified-hosts# - Currently Commented out - Script needs to be updated- Waiting for updates to the script -AR Ron - Bruno Muniz showed interest in creating DOC Videos supporting the StarlingX Installation Process. To check with Ildiko / Greg whether this is ok. These Videos can be hosted in a location in StarlingX. The Installation Docs can point to these videos - AR Bruno to get approvals from Ildiko / Greg - Sphinx Tools - Need to have further discussions about the version used upstream vs. downstream - AR Ron -To determine version. - Docker Container upstream / downstream - AR Ron (Discuss it with Greg / Ildiko) - a long term project - Operations Guide Archive - On Hold until further clarifications are discussed with Greg (https://review.opendev.org/c/starlingx/docs/+/822030) - OpenInfra Summit & PTG Recording: https://ptg.opendev.org/etherpads.html - Workshop Details are tracked in https://etherpad.opendev.org/p/stx_hands_on_workshop_2023 - IRC: (Note: This option is being evaluated) IRC channel for communication with the community. Team can use https://www.icechat.net/site/icechat-9/ as an alternate text editor from their browser. IRC is a chat platform, for text-based communication. There?s a web client for easy access: https://webchat.oftc.net/- You need to pick a nickname, and the channel name is #opendev. Once you are in the #opendev channel, you can talk to the group of people in that channel. To Setup IRC ? contributor-guide documentation (openstack.org) IRC here: https://docs.openstack.org/contributors/common/irc.html; Engineering Status: StarlingX Eng Stx Status: https://etherpad.opendev.org/p/stx-status StarlingX Eng Status 2023 https://etherpad.opendev.org/p/stx-cores ____________________________ 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 Jackie.Huang at windriver.com Mon Jul 31 04:56:39 2023 From: Jackie.Huang at windriver.com (Huang, Jie (Jackie)) Date: Mon, 31 Jul 2023 04:56:39 +0000 Subject: [Starlingx-discuss] StarlingX CI/CD setup on Arm platform In-Reply-To: References: Message-ID: Hi, Scott Kamp and Scott Little, I found the following actions in the meeting minutes in stx-status | OpenDev Etherpad: o ARM Support ? Action: Scott Kamp to respond to Jackie/the mailing list to provide assistance/access to some arm machines ? Action: Scott Little to respond regarding build questions ? Cannot mirror more files on CENGN; will need to wait until we transition away from CENGN ? Action: Scott Kamp to explore providing a hosting env temporarily So I think you might be able to help on Trevor?s and my questions: There would be 6 Arm servers contributed to our community for CI/CD (2 for build, 4 for testing of different deployment configs), what we want to know is: 1. What needs to be done for the CICD workflow setup and how? * E.g. how to setup build servers and testing env? * What CICD tools need to be setup? Zuul/Jenkins/etc. * Are there any docs for these setups? 2. How many efforts and how long will it take? 3. Is there a CICD team or someone that can help on the setup or just providing useful information? Thanks, Jackie From: Trevor Tao Sent: Thursday, July 27, 2023 5:06 PM To: Geary, Stephen (Steve) ; starlingx-discuss at lists.starlingx.io Cc: Huang, Jie (Jackie) Subject: StarlingX CI/CD setup on Arm platform Hi Steve, StarlingX: From the OS distro meeting yesterday, we knew that there would be 6 Arm servers contributed to our community to do the CI/CD related work. So we would like to ask who can help on the setup of CI/CD environment on the arm platform, and any other useful information/details for the CI/CD issue here. Thanks, Best Regards, Zijin Tao(Trevor Tao, ???) ARM Electronic Technology (Shanghai) Co., Ltd ?????????????? Building 11, Shanghai Busininess Park? , No.1016 Tianlin Rd, Minhang District, Shanghai, 200233 China ?????????1016???????2??10??200233 Cell: +86-153 7109 6192 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko at openinfra.dev Mon Jul 31 14:29:12 2023 From: ildiko at openinfra.dev (Ildiko Vancsa) Date: Mon, 31 Jul 2023 16:29:12 +0200 Subject: [Starlingx-discuss] TSC & Community call in the APAC-friendly time slot this week Message-ID: <0A0C1584-B00F-4785-82F1-925ED7664F83@openinfra.dev> Hi StarlingX Community, It is a friendly reminder that this week?s TSC & Community Call will be in the APAC friendly time slot. The call is scheduled to happen on August 2 at 7pm US Pacific Time / 10m pm US Eastern Time | August 3 at 0200 UTC / 10am China Standard Time. You can find dial-in information and further details here: https://wiki.openstack.org/wiki/Starlingx/Meetings#7pm_Pacific_on_Every_First_Wednesday_of_the_Month-_Technical_Steering_Committee_.26_Community_Call Best Regards, Ildik? ??? Ildik? V?ncsa Director of Community Open Infrastructure Foundation