From today's meeting:
* Standing Topics
* Build/Sanity
* similar to previous weeks, but now there's a 3rd Launchpad on the list: * from http://lists.starlingx.io/pipermail/starlingx-discuss/2021-April/011140.html * Status: YELLOW * The Setup and Provision are PASSING. * The daily sanity is FAILING on all configurations for test: test_reapply_openstack, but openstack commands are working correctly. * This might be related to bugs: * https://bugs.launchpad.net/starlingx/+bug/1917308 * https://bugs.launchpad.net/starlingx/+bug/1918420 * https://bugs.launchpad.net/starlingx/+bug/1922719 * per Frank, all 3 of these bugs should be resolved today, so we should not see them in the next sanity (notwithstanding some issue with repo sync that's currently being seen)
* Gerrit Reviews in Need of Attention * https://review.opendev.org/c/starlingx/openstack-armada-app/+/768388, several +1 already , need 2 +2, * https://review.opendev.org/c/starlingx/utilities/+/783128 stx-ceph-manager docker image build , need another +2.
* Topics for this Week
* stx.5.0
* gating bugs * etherpad: https://etherpad.opendev.org/p/stx-gating-bugs * list of all critical/high launchpads: * https://bugs.launchpad.net/starlingx/+bugs?field.searchtext=&orderby=-im... * anything else for stx.5.0?
* container image list * per Nic, 2 sources for the Sanity team * helm charts * CENGN mirror http://mirror.starlingx.cengn.ca/mirror/starlingx/master/centos/ * Bill will open a discussion on the mailing list on this topic
* ARs from Previous Meetings *
* Open Requests for Help
* [Sanath Kumar] * 1. Once the Setup and Provisioning are done we will get Controller-0. (Installing StarlingX) * After Provisioning Step If I run the command ping www.google.in, I will get the error message as ping: www.google.in: Name or service not known. * After this step, if I do sudo reboot, everything will be normal and I will be able to ping: www.google.in. But Controller-0 will be destroyed when we reboot in the server. * I need to do the Setup and Provisioning step once again to install controller-0, but if I give ping www.google.in, I will get the error message as ping: www.google.in: Name or service not known as it was before. * Can you please let me know what can be done so that I can overcome this issue? * there were no comments in the community call other than possibly a networking issue * 2. When we install StarlingX, It creates a VM (controller-0), which will be CentOS-7 by default. Is there any way where I can make Controller-0 to some other Operating System or Upgrade CentOS-7 to a higher version? * can't change the host OS
* Securing the traffic between Central cloud and edge cloud * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-April/011122.html * no comments on the community call other than possibly a networking question
* Preparation of storage server * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-April/011125.html * refer to the Storage Guide in the docs
* Deploying controller-1 and N number of worker nodes * http://lists.starlingx.io/pipermail/starlingx-discuss/2021-April/011126.html * Nic will respond to this
* Build Matters (if required) * nothing this week
-----Original Message----- From: Zvonar, Bill Sent: Tuesday, April 6, 2021 12:49 PM To: starlingx-discuss@lists.starlingx.io Subject: Community (& TSC) Call (April 7, 2021)
Hi all, reminder of the weekly TSC/Community calls coming up tomorrow.
I put a couple of things on the community call agenda:
- stx.5.0 gating bugs (1 Critical, 4 High), see [4] - maintaining a container image list, as we've discussed a bit in previous calls
Please feel free to add other 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_S... [2] meeting start time in various time-zones: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210407T1400 [3] https://zoom.us/j/342730236?pwd=N21CUXNXVlJXMlcyZjZ0SE96cVNjQT09 [4] https://etherpad.opendev.org/p/stx-gating-bugs