[Starlingx-discuss] Community Call Meeting Minutes

[Ildiko Vancsa]

Hi Prashanthi,

Thank you for joining the meeting. What time were you on the Zoom bridge?

For the TSC & Community calls we have an alternated schedule. The community set this up to ensure that people in all time zones have the chance to participate in the meetings.

Call schedule:

* 7pm US Pacific Time, which is currently 0200 UTC, on every first Wednesday of the month
  - Dial-in details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7pm_Pacific_on_Every_First_Wednesday_of_the_Month-_Technical_Steering_Committee_.26_Community_Call

* 7am US Pacific Time, which is currently 1400 UTC, on the remaining Wednesdays of the month
  - Dial-in details: https://wiki.openstack.org/wiki/Starlingx/Meetings#7am_Pacific_-_Technical_Steering_Committee_.26_Community_Call


For the connectivity issues. Do you mean the IP allocation issue you sent an email about earlier: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-April/013940.html ? If this is the issue you would like to cover, can you please send more information about the error as a reply to your first email? For instance, what you were trying to do, what command you used and what the error message was.

Is this helpful?

Thanks and Best Regards,
Ildikó

———

Ildikó Váncsa
Director of Community
Open Infrastructure Foundation





> On Apr 5, 2023, at 21:55, Prashanthi Moligi <prashanthi.moligi at tcs.com> wrote:
> 
> TCS Confidential
> 
> Hi lldiko,
> 
> We tried joining this meeting yesterday, but only four members were there in meeting, waited for some time and quit the meeting, can you please share meeting link for weekly meeting so that we can join every week for our issues.
> 
> Also we are facing internet issues, in PC where we installed StarlingX iso image, want to discuss with regarding those issues, can you please help us in resolving these issues.
> 
> Thanks&Regards,
> Prashanthi.
> TCS.
> 
> -----Original Message-----
> From: Ildiko Vancsa <ildiko at openinfra.dev>
> Sent: Thursday, April 6, 2023 8:37 AM
> To: StarlingX ML <starlingx-discuss at lists.starlingx.io>
> Subject: [Starlingx-discuss] Community Call Meeting Minutes
> 
> "External email. Open with Caution"
> 
> Hi StarlingX community,
> 
> We had a handful of people on the Community call today. We decided to use the meeting to discuss some ongoing challenges and next steps.
> 
> Scott Kamp brought up a few items with regards to network configuration recommendations and challenges within the platform:
> 
> * Network bond + LAG
>  - The documentation suggests 3 networks in a standards setup. This translates to 6 interfaces when setting up a LAG, which is too many.
>  - Using VLAN as a workaround doesn’t always work, not every commercial network provider allows for that setup.
>  - There’s an issue with bonding in Debian Bullseye
>    + See the earlier email on starlingx-discuss: https://lists.starlingx.io/pipermail/starlingx-discuss/2023-March/013877.html
>    + —> Has anyone ran or looked into the above issue? ^^
> 
> * Wireguard
>  - While Wireguard is enabled on StarlingX, Wireguard tools is not. Scott and team are working on testing and adding it
> 
> * Calico support
>  - Scott and team are working with Calico and are planning to add that to the platform
>  - Scott will propose a spec to introduce the feature idea and move the conversation forward
> 
> * Addressing the lower attendance
>  - Wednesday was a public holiday in China, which probably affected attendance on Thursday morning
>  - Ildiko will look into advertising the APAC time slot call better in the region
> 
> Best Regards,
> Ildikó
> 
> ———
> 
> Ildikó Váncsa
> Director of Community
> Open Infrastructure Foundation
> 
> 
> 
> 
> 
> 
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> 
> TCS Confidential
> =====-----=====-----=====
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain 
> confidential or privileged information. If you are 
> not the intended recipient, any dissemination, use, 
> review, distribution, printing or copying of the 
> information contained in this e-mail message 
> and/or attachments to it are strictly prohibited. If 
> you have received this communication in error, 
> please notify us by reply e-mail or telephone and 
> immediately and permanently delete the message 
> and any attachments. Thank you
> 
>