[Starlingx-discuss] Community (& TSC) Call (Feb 17, 2021)

Zvonar, Bill Bill.Zvonar at windriver.com
Wed Feb 17 15:47:35 UTC 2021


>From today's call:

* Standing Topics

      * Sanity
            * currently red just for Standard Config on bare metal 
            * suspect commit identified: http://lists.starlingx.io/pipermail/starlingx-discuss/2021-February/010842.html
            * we agreed we can wait a day for the response to the mail above since this only impacts Standard Config on bare metal

      * Gerrit Reviews in Need of Attention
            * nothing this week 

* Topics for this Week
      * nothing this week 

* ARs from Previous Meetings
      * Bruce will check in next week on the RHEL Dup action 

* Open Requests for Help

      * Sanity-Test failed [sanath kumar]
            * Hello Team, as discussed in the previous meet, I have checked with all the documents and made changes accordingly.
                  * I request you to open this link and have look at the document https://drive.google.com/file/d/1vHx-GZ5mxAbnAiegK8jl7GqnjtokmaWf/view?usp=sharing 
                  * Please let me know what can be done next?
                  * per Nic, the 2 failing testcases are issues with the tests, so they can be ignored 
            * Sanath asked if the Degraded state will impact his deployment
                  * per Frank, it depends - check logs & alarms to see the specific reason for Degraded state 

      * [HSC] (Lokendra)
            * Openstack APPLICATION UPLOAD GETTING FAILED - with LAG Data Interface
                  * https://bugs.launchpad.net/starlingx/+bug/1915231
                  * not screened yet, should be done this week
            * how to enable Debug logs in /var/log/sysinv.log file
                  * per Bart, should be able to do this by editing the /etc/sysinv/sysinv.config file & restart the service

      * Starlingx integration with Open Source Mano (OSM) (Sin Lam Tan)
            * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-February/010830.html
            * Austin has responded 

      * StarlingX - 4.0 build issue (Sriram)
            * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-February/010828.html
            * Scott responded re: possible proxy/network issues (Scott has no issues reaching)

      * Moving from Simplex to Distribute (Danishka)
            * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-February/010834.html
            * per Bart the answer is no, Bill will respond 

      * Questions on StarlingX upgrades (Pratik)
            * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-February/010844.html
            * Bart will review & respond 

      * Issue applying helm chart in horizon container with custom dashboard changes (Haridhar)
            * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-February/010845.html
            * no comments 

* Build Matters (if required)
      * nothing to discuss this week, per Scott there were 6 of 7 clean builds
      * one build saw issues related to our mirror of the Kata repo 
      * (may have been a side effect of the issues we had a couple of weeks ago)

---

From: Zvonar, Bill 
Sent: Wednesday, February 17, 2021 7:41 AM
To: starlingx-discuss at lists.starlingx.io
Subject: Community (& TSC) Call (Feb 17, 2021)

Hi all, reminder of the weekly TSC/Community calls coming up later today.

Please feel free to add items to the agenda [0] for the community call.

Bill...

[0] etherpad: https://etherpad.openstack.org/p/stx-status
[1] call details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call
[2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210217T1500
[3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09



More information about the Starlingx-discuss mailing list