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

Keyboard Shortcuts

Thread View

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

Starlingx-discuss

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

  • 2 participants
  • 8219 discussions
[Starlingx-discuss] Intentions toward enhancements for Starlingx Libvirt deployment method host utilization
by Thebeau, Michel 11 Jul '23

11 Jul '23
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-89… 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 <memory>) Add an override variable for the CPU setting of each node (currently XML hardcoded <vcpu>) 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.
3 7
0 0
[Starlingx-discuss] Sanity Master Test LAYERED build ISO 20230706T060000Z
by Peng, Peng 11 Jul '23

11 Jul '23
Sanity Test from 2023 July 10 (https://mirror.starlingx.cengn.ca/mirror/starlingx/master/debian/monolithic…) Status: GREEN SX sanity Passed: 17 (100.0%) Failed: 0 (0.0%) Total Executed: 17 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_isolated_2p_2_big_pod_best_effort_HT_AIO PASS test_sriovdp_netdev_single_pod[1-1-lock/unlock] PASS test_sriovdp_netdev_connectivity_ipv4[1-1-calico-ipam] PASS test_sriovdp_mixed_add_vf_interface[1] PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] DX sanity Passed: 19 (100.0%) Failed: 0 (0.0%) Total Executed: 19 List of Test Cases: ------------------------------------------------------ PASS test_system_health_pre_session[pods] PASS test_system_health_pre_session[alarms] PASS test_system_health_pre_session[system_apps] PASS test_horizon_host_inventory_display PASS test_lock_unlock_host PASS test_swact_controller_platform PASS test_pod_to_pod_connection PASS test_pod_to_service_connection PASS test_host_to_service_connection PASS test_push_docker_image_to_local_registry_active PASS test_push_docker_image_to_local_registry_standby PASS test_upload_charts_via_helm_upload PASS test_host_operations_with_custom_kubectl_app PASS test_force_reboot_host[active_controller-True] PASS test_force_reboot_host[active_controller-False] PASS test_force_reboot_host[standby_controller-False] PASS test_bmc_verify_bm_type_ipmi PASS test_system_coredumps_and_crashes[core_dumps] PASS test_system_coredumps_and_crashes[crash_reports] Regards, PV team
1 0
0 0
[Starlingx-discuss] Fwd: vPTG October 2023 Dates & Registration Kickoff
by Kendall Nelson 10 Jul '23

10 Jul '23
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/
1 0
0 0
[Starlingx-discuss] Bi-Weekly StartlingX OS Distro & Multi-OS Meeting: May 31, 2023
by Wang, Linda 10 Jul '23

10 Jul '23
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
1 0
0 0
[Starlingx-discuss] Proposal to add Luan Utimura for core reviewer in the "openstack-armada-app" repo
by Cervi, Thales Elero 10 Jul '23

10 Jul '23
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
5 4
0 0
[Starlingx-discuss] How to get standby controller as active after active controller down
by open infra 10 Jul '23

10 Jul '23
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
2 1
0 0
[Starlingx-discuss] proposal to add Jim Gauld for core reviewer in the "config" repo
by Chris Friesen 10 Jul '23

10 Jul '23
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
3 2
0 0
[Starlingx-discuss] TSC & Community Call is canceled this week
by Ildiko Vancsa 05 Jul '23

05 Jul '23
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_… Best Regards, Ildikó ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
1 0
0 0
[Starlingx-discuss] Canceled: StarlingX TSC & Community Call [APAC Friendly Time]
by Khalil, Ghada 04 Jul '23

04 Jul '23
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
1 0
0 0
[Starlingx-discuss] TSC & Community Call - July 5/2023 -- no WR participation
by Khalil, Ghada 04 Jul '23

04 Jul '23
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
2 2
0 0
  • ← Newer
  • 1
  • ...
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • ...
  • 822
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.