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 -----
  • 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

May 2020

  • 53 participants
  • 159 discussions
[Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 365 - Failure!
by build.starlingx@gmail.com 25 May '20

25 May '20
Project: STX_build_pre_installer_layered Build #: 365 Status: Failure Timestamp: 20200525T191421Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/2020… -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20200525T190356Z DOCKER_BUILD_ID: jenkins-master-distro-20200525T190356Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/2020… FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200525T190356Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro BUILD_ISO: false
1 0
0 0
[Starlingx-discuss] [Build] This playbook is not compatible with Starlingx software version 20.06
by Scott Little 25 May '20

25 May '20
On Friday the PLATFORM_RELEASE (aka SW_VERSION) value was changed to 20.06.  The matching update in ansible-playbook got stuck in zuul, and failed to merge until I triggered a zuul retry not long ago. Monolithic loads timestamped 20200523T080014Z, 20200524T080012Z, 20200525T080011Z will fail to configure with error message...    "This playbook is not compatible with Starlingx software version 20.06" Layered build over this time range are also broken. I have trigger a new monolithic build in CENGN to pick up the fix. Scott
1 0
0 0
[Starlingx-discuss] Minutes: StarlingX Release Meeting - May 21/2020
by Khalil, Ghada 25 May '20

25 May '20
Agenda/Minutes are posted at: https://etherpad.openstack.org/p/stx-releases stx.4.0 - Feature Status - https://docs.google.com/spreadsheets/d/1a93wt0XO0_JvajnPzQwnqFkXfdDysKVnHpb… - Selective Feature Updates - FPGA Integration - Need to reduce scope. - Don't expect Distributed Cloud orchestration code to make it for stx.4.0. - Will limit the scope to flashing images thru the config subsystem via the system cmds. - Also have a dependency on Intel's most recent OPAE/SDK being upstreamed. - Ceph Containerization - Update from Austin - Team addressing some issues currently , it should be ready before May 29th. - system host-swact for duplex . - system backup/restore feature for containerization ceph - Requesting code review feedback - https://review.opendev.org/#/q/status:open+branch:master+topic:%22ceph+cont… - Feature Testing - https://docs.google.com/spreadsheets/d/1C9n4aRQT7xMyTDCT5sfuZGNI9ermAX5BYRy… - Noteables: - Ceph Rook: Need to re-work the test-cases - B&R: Waiting for a number of bug fixes; currently B&R is not working - TSN: Started to look into the documentation and building the kernel. Working to get setup ready to start testing. - Regression Testing - https://docs.google.com/spreadsheets/d/1gA3bnLS7aY2y8dKxm4MuqpWyELq3PVJMYti… - Test team has concerns about completing regression in time - Robot automation is not running in a fully automated fashion - They were run previously in a semi-automated fashion where the tester would setup what the test needed manually - This is becoming very time consuming for the new test team as they don't have this background information - Investigating test failures to determine what is wrong - Team is also looking at re-implementing some of the test-cases in - Still need to assess the full impact of this on the release time-frame - Automated pytest is starting - Bugs - Need to start focusing on bug resolution - https://bugs.launchpad.net/starlingx/+bugs?field.tag=stx.4.0 - Current Count: 90 - Add as a PSA in the community meeting Maintenance Releases - stx.2.x - Nobody in the community came back with a response that they are using stx.2.0 and need a maintenance release. - Agreed not to proceed with any stx.2.x maintenance releases - stx.3.x - No specific demand from the community for stx.3.x maintenance release - Got a response from one user (Volker von Hoesslin) saying stx.3.0 is working fine for him. His interest was more in the upgrade to stx.4.0 - Agreed to wait for the upgrades enabling code (see below) before considering an stx.3 maintenance release - Forecast post-June -- Daet to be confirmed later based on upgrades plan stx.3 to stx.4 Upgrades - Question (Bruce): What is required for this? - There is code that will be required on the stx.3 side to enable upgrades from the stx.3 side to the stx.4 side - This code is not ready yet. There is no plan yet as to when this will code will be ready. - Team has been focusing on the framework and allowing a "null" upgrade from stx.4 to stx.4 - This is the current commitment for stx.4.0 - The framework code is currently going in stx master - After stx.4.0 (end of June), team will look at what portion of code is required to be ported to the stx.3 release - The stx.3 code can be included in a maintenance release OR a user can make it into a patch if they want to avoid a re-install to the stx.3 maintenance release.
1 0
0 0
[Starlingx-discuss] [TSC] Minutes from the May 20th TSC call
by Jolliffe, Ian 25 May '20

25 May '20
* Virtual PTG – dates are : June 1st to 5th – Register here: https://www.eventbrite.com/e/virtual-project-teams-gathering-june-2020-tick… o Kata joint session: "I would propose having a one hour time slot on June 2 between UTC 13-17. I think that would work for most of the Kata community folks attending the PTG. (https://etherpad.opendev.org/p/2020-ptg-kata-prepare)" § http://lists.katacontainers.io/pipermail/kata-dev/2020-May/001354.html § https://doodle.com/poll/nnzynksqgmyt4d5g o 13:00 UTC - is the agreed time. * License review - comment from Thierry - what is our process to ensure our ongoing compliance. o Look for Foundation license process and policy - can we follow § Following OSI policy § Can we follow - the OpenStack process? Integrated projects is a bit different. § add to checklist for core reviewers o https://governance.openstack.org/tc/reference/licensing.html o To be discussed again next week * OSF Board meeting is on June 11 (ildikov) o https://wiki.openstack.org/wiki/Governance/Foundation/11June2020BoardMeeting o Ian and Saul to co-present
1 0
0 0
[Starlingx-discuss] Adding Ian Jolliffe candidacy for StarlingX TSC role
by Jolliffe, Ian 25 May '20

25 May '20
StarlingX is an exciting and growing project to which I have had the honor and privilege to contribute to from its launch. I am a founding member of the TSC and over the past 2 years I have helped facilitate the TSC, welcome new members and help guide the project from a technical perspective. I am a frequent speaker at industry events on the values of StarlingX and share my passion for edge computing widely. I see edge as having the ability to transform people's lives through transformation of technology used in communications networks, health care and transportation - StarlingX is a big part of making that happen. I have a deep technical knowledge of distributed computing and optimization of edge focused solutions. I have helped out in the Edge Computing talk selection committee for the Shanghai summit. I was honored and humbled to receive a community award at the Denver summit, for my contributions to the StarlingX project - [0] On the TSC I would continue to have the following areas of focus: - Continue to advocate for the 4 Opens model of development. - My goal is to champion and contribute to increasing test focus a and culture of the project around test. - This area is so important to the health of any open source project. - This will help new developers contribute more easily and the project to grow the contribution base and speed of development. - We had a test focused Hack-a-thon and plan on working to set up another one later this year. Growing the community, maintaining the technical relevance of the project and continuing StarlingX's journey to a diverse and thriving open source project are goals I want to contribute to for StarlingX. Thank you for your consideration of me as a candidate to be re-elected to the TSC for a second term. [0] https://superuser.openstack.org/articles/open-infrastructure-community-cont…
1 0
0 0
[Starlingx-discuss] StarlingX TSC election - Nomination period started
by Ildiko Vancsa 25 May '20

25 May '20
Hi StarlingX Community, Nominations for the 4 Technical Steering Committee positions are now open and will remain open until __May 26, 2020 20:00 UTC__. All nominations must be submitted as a text file to the starlingx/election repository as explained on the election website[1]. Please note that the name of the file should match the email address in your Gerrit configuration. Candidates for the Technical Steering Committee Positions: Any contributing community member can propose their candidacy for an available, directly-elected TSC seat. The election will be held from June 2, 2020 20:00 UTC through to June 9, 2020 20:00 UTC. The electorate are the community members that are also contributors for one of the official teams[2] or served in a leadership role (TSC, PL, TL) over the 12-month timeframe May 19, 2019 to May 19, 2020, as well as the contributors who are acknowledged by the TSC. Please see the website[3] for additional details about this election. Please find below the timeline: TC nomination starts @ May 19, 2020 20:00 UTC TC nomination ends @ May 26, 2020 20:00 UTC TC campaigning starts @ May 26, 2020 20:00 UTC TC campaigning ends @ June 2, 2020 20:00 UTC TC elections starts @ June 2, 2020 20:00 UTC TC elections ends @ June 9, 2020 20:00 UTC If you have any questions please be sure to either ask them on the mailing list or to the elections officials[4]. Thank you, [1] https://docs.starlingx.io/election/#how-to-submit-a-candidacy [2] https://docs.starlingx.io/governance/reference/tsc/projects/index.html [3] https://docs.starlingx.io/election/ [4] https://docs.starlingx.io/election/#election-officials
1 1
0 0
[Starlingx-discuss] [build-report] STX_build_layer_distro_master_master - Build # 127 - Still Failing!
by build.starlingx@gmail.com 24 May '20

24 May '20
Project: STX_build_layer_distro_master_master Build #: 127 Status: Still Failing Timestamp: 20200524T230155Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/2020… -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false
1 0
0 0
[Starlingx-discuss] [build-report] STX_build_pre_installer_layered - Build # 363 - Failure!
by build.starlingx@gmail.com 24 May '20

24 May '20
Project: STX_build_pre_installer_layered Build #: 363 Status: Failure Timestamp: 20200524T231200Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/2020… -------------------------------------------------------------------------------- Parameters MY_WORKSPACE: /localdisk/loadbuild/jenkins/master-distro/20200524T230155Z DOCKER_BUILD_ID: jenkins-master-distro-20200524T230155Z-builder OS: centos MY_REPO: /localdisk/designer/jenkins/master-distro/cgcs-root PUBLISH_LOGS_URL: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/2020… FULL_BUILD: false PUBLISH_LOGS_BASE: /export/mirror/starlingx/master/centos/distro/20200524T230155Z/logs MASTER_JOB_NAME: STX_build_layer_distro_master_master LAYER: distro MY_REPO_ROOT: /localdisk/designer/jenkins/master-distro BUILD_ISO: false
1 0
0 0
Re: [Starlingx-discuss] Docker Image Build guide for Layer Build
by Das, Ambarish 23 May '20

23 May '20
+ starlingX-disucss list From: Das, Ambarish Sent: Friday, May 22, 2020 12:08 PM To: Scott Little <scott.little(a)windriver.com> Cc: Wold, Saul <saul.wold(a)intel.com>; Mukherjee, Sanjay K <sanjay.k.mukherjee(a)intel.com>; Gopi <gopalkrishna.bhat(a)intel.com> Subject: Docker Image Build guide for Layer Build Hi Scott, I am trying to build docker image for FM containerization following the build guide below but it seems this is valid for monolithic build only. https://docs.starlingx.io/developer_resources/build_docker_image.html I have changed one file (stx-upstream/openstack/python-horizon/centos/stx-horizon.stable_docker_image) in distro layer and want to build a docker image. Could you please let me know if any modifications necessary for layered build corresponding to this doc? Thanks & regards, Ambarish StarlingX Team,BA
1 0
0 0
[Starlingx-discuss] [build-report] STX_build_layer_distro_master_master - Build # 126 - Still Failing!
by build.starlingx@gmail.com 23 May '20

23 May '20
Project: STX_build_layer_distro_master_master Build #: 126 Status: Still Failing Timestamp: 20200524T013151Z Check logs at: http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/distro/2020… -------------------------------------------------------------------------------- Parameters FULL_BUILD: false FORCE_BUILD: false
1 0
0 0
  • ← Newer
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • ...
  • 16
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.