Updating the overview slide deck
Hi StarlingX Community, I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website. The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn. I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them? Thanks and Best Regards, Ildikó [1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
Hey Ildiko, I took a look at the StarlingX Overview Slide Deck. ( NOTE … I have questions for @Ngo, Tee<mailto:Tee.Ngo@windriver.com>, @Webster, Steven<mailto:Steven.Webster@windriver.com>, @Reed, Joshua<mailto:Joshua.Reed@windriver.com> … below. ) Some ideas on updates that could be done: * Add Geo-Redundancy of Central Cloud in Distributed Cloud configurations * SLIDE 6 * @Ngo, Tee<mailto:Tee.Ngo@windriver.com> do you have a Geo-Redundancy diagram that you could share with Ildiko ? * SLIDE 9 - StarlingX - Edge Virtualization Platform * i.e. very very high-level software architecture diagram * changes ? * under OpenStack Components * remove ‘Bare Metal’ and ‘Object Storage’ blocks * they are not supported * under Kubernetes Components * I would change ‘DNS Service’ to ‘Core DNS’ … I believe that is what it is referring to, @Webster, Steven<mailto:Steven.Webster@windriver.com> ? and * What is Network Proxy referring to ? CNI ? Should we just change that to ‘CNI’ or ‘Container Networking’ ? @Webster, Steven<mailto:Steven.Webster@windriver.com> ? * We should similarly add ‘CSI’ or ‘Container Storage’ * We should change ‘Helm’ to ‘FluxCD, Helm’ * We should change ‘Dashboard’ to ‘Kubectl , Dashboard’ * I would add a block for ‘Integrated OpenSource Container Services’ * i.e. for all the open-source containerized services that we integrate into solution * e.g. nginx, cert-manager, metrics server, istio, vault, dex, kubevirt, security profiles operator, portieris, etc. * for the layer just above Linux * Remove Armada * For the Linux Layer * change to ‘Linux - Debian’ ? * SLIDE 10 * Change the ‘Kubernetes + OpenStack’ block to just ‘Kubernetes’ * OpenStack is in the Containerized block above it * SLIDE 11 * For the ORANGE layer * Remove ‘TPM’ block … not supported anymore * we have plans to add it back in … but not sure when that will happen * For the GREEN layer * Change ‘Low Latency Linux’ * to: ‘Standard or Low Latency Linux - Debian’ * SLIDE 12 * For scalability bullet … should replace with something like * Scalable deployment models * For Standalone Cloud * Support 1-200 k8s workers * Support 1-10 k8s workers configured as OpenStack computes ( maybe don’t say this one … its embarrassing 😉 ) * For Distributed Cloud * Support 1-1,000 Subclouds * where each Subcloud is a cloud of 1-200 k8s workers * The bullet on “Focus on minimizing the infrastructure footprint” is not well written … not understandable Suggested REWORD * Minimize infrastructure footprint / overhead * For Standard (Controllers + Workers) Configuration * support 2-server controller/master solution * on worker nodes, only 1 core required for StarlingX Platform * For All-In-One (AIO) Configurations (i.e. AIO-Simplex and AIO-Duplex) * AIO servers require only 2 cores for StarlingX Platform * SLIDE 20 “Kubernetes Cluster Software Components” * Change Armada to FluxCD * Personally I would change ‘Ingress LB’ to ‘Nginx’ … to avoid any confusion * I would remove the current and future stuff * SLIDE 26 “Application Management” * Need to change the Armada stuff to FluxCD * @Reed, Joshua<mailto:Joshua.Reed@windriver.com> ? Could you provide updated text and diagram for this slide ? * SLIDE 29 Supported OpenStack Servies * Should remove * Ironic and Telemetry(Ceilometer Gnocchi Panko Aodh) * … not currently supported. * SLIDE 32 & 33 … on Distributed Cloud * @Ngo, Tee<mailto:Tee.Ngo@windriver.com> ? can you provide updated text for these two slides … and diagram if you feel its required Greg. From: Ildiko Vancsa <ildiko@openinfra.dev> Sent: Tuesday, May 7, 2024 8:47 PM To: StarlingX ML <starlingx-discuss@lists.starlingx.io> Subject: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website. The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn. I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them? Thanks and Best Regards, Ildikó [1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf<https://urldefense.com/v3/__https:/www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf__;!!AjveYdw8EvQ!aLMbd-Zp0RAKZzHdz0vnKmY1M2kRSHpJH06E1lrlZLd3qht35WHnYBki8vau1htFnOr0K5qu29HNkrPP0Pz3_Qsg$> ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
Thanks Greg for your input! I will wait for responses from people you tagged, as well as any further comments before starting to edit the slide deck. Does anyone have further comments on what needs to be updated in the StarlingX overview slide deck? Best Regards, Ildikó ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
On May 16, 2024, at 5:00 AM, Waines, Greg <Greg.Waines@windriver.com> wrote:
Hey Ildiko, I took a look at the StarlingX Overview Slide Deck.
( NOTE … I have questions for @Ngo, Tee <mailto:Tee.Ngo@windriver.com>, @Webster, Steven <mailto:Steven.Webster@windriver.com>, @Reed, Joshua <mailto:Joshua.Reed@windriver.com> … below. )
Some ideas on updates that could be done: Add Geo-Redundancy of Central Cloud in Distributed Cloud configurations SLIDE 6 @Ngo, Tee <mailto:Tee.Ngo@windriver.com> do you have a Geo-Redundancy diagram that you could share with Ildiko ? SLIDE 9 - StarlingX - Edge Virtualization Platform i.e. very very high-level software architecture diagram changes ? under OpenStack Components remove ‘Bare Metal’ and ‘Object Storage’ blocks they are not supported under Kubernetes Components I would change ‘DNS Service’ to ‘Core DNS’ … I believe that is what it is referring to,@Webster, Steven <mailto:Steven.Webster@windriver.com> ? and What is Network Proxy referring to ? CNI ? Should we just change that to ‘CNI’ or ‘Container Networking’ ? @Webster, Steven <mailto:Steven.Webster@windriver.com> ? We should similarly add ‘CSI’ or ‘Container Storage’ We should change ‘Helm’ to ‘FluxCD, Helm’ We should change ‘Dashboard’ to ‘Kubectl , Dashboard’ I would add a block for ‘Integrated OpenSource Container Services’ i.e. for all the open-source containerized services that we integrate into solution e.g. nginx, cert-manager, metrics server, istio, vault, dex, kubevirt, security profiles operator, portieris, etc. for the layer just above Linux Remove Armada For the Linux Layer change to ‘Linux - Debian’ ? SLIDE 10 Change the ‘Kubernetes + OpenStack’ block to just ‘Kubernetes’ OpenStack is in the Containerized block above it SLIDE 11 For the ORANGE layer Remove ‘TPM’ block … not supported anymore we have plans to add it back in … but not sure when that will happen For the GREEN layer Change ‘Low Latency Linux’ to: ‘Standard or Low Latency Linux - Debian’ SLIDE 12 For scalability bullet … should replace with something like Scalable deployment models For Standalone Cloud Support 1-200 k8s workers Support 1-10 k8s workers configured as OpenStack computes ( maybe don’t say this one … its embarrassing 😉 ) For Distributed Cloud Support 1-1,000 Subclouds where each Subcloud is a cloud of 1-200 k8s workers The bullet on “Focus on minimizing the infrastructure footprint” is not well written … not understandable Suggested REWORD Minimize infrastructure footprint / overhead For Standard (Controllers + Workers) Configuration support 2-server controller/master solution on worker nodes, only 1 core required for StarlingX Platform For All-In-One (AIO) Configurations (i.e. AIO-Simplex and AIO-Duplex) AIO servers require only 2 cores for StarlingX Platform SLIDE 20 “Kubernetes Cluster Software Components” Change Armada to FluxCD Personally I would change ‘Ingress LB’ to ‘Nginx’ … to avoid any confusion I would remove the current and future stuff SLIDE 26 “Application Management” Need to change the Armada stuff to FluxCD @Reed, Joshua <mailto:Joshua.Reed@windriver.com> ? Could you provide updated text and diagram for this slide ? SLIDE 29 Supported OpenStack Servies Should remove Ironic and Telemetry(Ceilometer Gnocchi Panko Aodh) … not currently supported. SLIDE 32 & 33 … on Distributed Cloud @Ngo, Tee <mailto:Tee.Ngo@windriver.com> ? can you provide updated text for these two slides … and diagram if you feel its required
Greg.
From: Ildiko Vancsa <ildiko@openinfra.dev <mailto:ildiko@openinfra.dev>> Sent: Tuesday, May 7, 2024 8:47 PM To: StarlingX ML <starlingx-discuss@lists.starlingx.io <mailto:starlingx-discuss@lists.starlingx.io>> Subject: Updating the overview slide deck
CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community,
I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website.
The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn.
I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them?
Thanks and Best Regards, Ildikó
[1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf <https://urldefense.com/v3/__https:/www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf__;!!AjveYdw8EvQ!aLMbd-Zp0RAKZzHdz0vnKmY1M2kRSHpJH06E1lrlZLd3qht35WHnYBki8vau1htFnOr0K5qu29HNkrPP0Pz3_Qsg$>
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
Hey Ildiko thanks for taking this initiative and sorry for the slow response! I’ll leave comments to Greg’s questions inline marked with [> steve]:. From: Ildiko Vancsa <ildiko@openinfra.dev> Sent: Wednesday, May 22, 2024 12:46 AM To: Waines, Greg <Greg.Waines@windriver.com> Cc: StarlingX ML <starlingx-discuss@lists.starlingx.io>; Ngo, Tee <Tee.Ngo@windriver.com>; Webster, Steven <Steven.Webster@windriver.com>; Reed, Joshua <Joshua.Reed@windriver.com> Subject: Re: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks Greg for your input! I will wait for responses from people you tagged, as well as any further comments before starting to edit the slide deck. Does anyone have further comments on what needs to be updated in the StarlingX overview slide deck? Best Regards, Ildikó ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation On May 16, 2024, at 5:00 AM, Waines, Greg <Greg.Waines@windriver.com<mailto:Greg.Waines@windriver.com>> wrote: Hey Ildiko, I took a look at the StarlingX Overview Slide Deck. ( NOTE … I have questions for @Ngo, Tee<mailto:Tee.Ngo@windriver.com>, @Webster, Steven<mailto:Steven.Webster@windriver.com>, @Reed, Joshua<mailto:Joshua.Reed@windriver.com> … below. ) Some ideas on updates that could be done: * Add Geo-Redundancy of Central Cloud in Distributed Cloud configurations * SLIDE 6 * @Ngo, Tee<mailto:Tee.Ngo@windriver.com> do you have a Geo-Redundancy diagram that you could share with Ildiko ? * SLIDE 9 - StarlingX - Edge Virtualization Platform * i.e. very very high-level software architecture diagram * changes ? * under OpenStack Components * remove ‘Bare Metal’ and ‘Object Storage’ blocks * they are not supported * under Kubernetes Components * I would change ‘DNS Service’ to ‘Core DNS’ … I believe that is what it is referring to,@Webster, Steven<mailto:Steven.Webster@windriver.com> ? and [> steve]: I think that’s fine ^ * What is Network Proxy referring to ? CNI ? [> steve]: Yeah this is kind of a weird one. I think it would be much better referred to as you say below by “CNI”. Should we just change that to ‘CNI’ or ‘Container Networking’ ? @Webster, Steven<mailto:Steven.Webster@windriver.com> ? [> steve]: I think “CNI” is fine to keep as it’s commonly used in the community and it probably makes it easier to fit on the diagram. * We should similarly add ‘CSI’ or ‘Container Storage’ * We should change ‘Helm’ to ‘FluxCD, Helm’ * We should change ‘Dashboard’ to ‘Kubectl , Dashboard’ * I would add a block for ‘Integrated OpenSource Container Services’ * i.e. for all the open-source containerized services that we integrate into solution * e.g. nginx, cert-manager, metrics server, istio, vault, dex, kubevirt, security profiles operator, portieris, etc. * for the layer just above Linux * Remove Armada * For the Linux Layer * change to ‘Linux - Debian’ ? * SLIDE 10 * Change the ‘Kubernetes + OpenStack’ block to just ‘Kubernetes’ * OpenStack is in the Containerized block above it * SLIDE 11 * For the ORANGE layer * Remove ‘TPM’ block … not supported anymore * we have plans to add it back in … but not sure when that will happen * For the GREEN layer * Change ‘Low Latency Linux’ * to: ‘Standard or Low Latency Linux - Debian’ * SLIDE 12 * For scalability bullet … should replace with something like * Scalable deployment models * For Standalone Cloud * Support 1-200 k8s workers * Support 1-10 k8s workers configured as OpenStack computes ( maybe don’t say this one … its embarrassing 😉 ) * For Distributed Cloud * Support 1-1,000 Subclouds * where each Subcloud is a cloud of 1-200 k8s workers * The bullet on “Focus on minimizing the infrastructure footprint” is not well written … not understandable Suggested REWORD * Minimize infrastructure footprint / overhead * For Standard (Controllers + Workers) Configuration * support 2-server controller/master solution * on worker nodes, only 1 core required for StarlingX Platform * For All-In-One (AIO) Configurations (i.e. AIO-Simplex and AIO-Duplex) * AIO servers require only 2 cores for StarlingX Platform * SLIDE 20 “Kubernetes Cluster Software Components” * Change Armada to FluxCD * Personally I would change ‘Ingress LB’ to ‘Nginx’ … to avoid any confusion * I would remove the current and future stuff * SLIDE 26 “Application Management” * Need to change the Armada stuff to FluxCD * @Reed, Joshua<mailto:Joshua.Reed@windriver.com> ? Could you provide updated text and diagram for this slide ? * SLIDE 29 Supported OpenStack Servies * Should remove * Ironic and Telemetry(Ceilometer Gnocchi Panko Aodh) * … not currently supported. * SLIDE 32 & 33 … on Distributed Cloud * @Ngo, Tee<mailto:Tee.Ngo@windriver.com> ? can you provide updated text for these two slides … and diagram if you feel its required Greg. From: Ildiko Vancsa <ildiko@openinfra.dev<mailto:ildiko@openinfra.dev>> Sent: Tuesday, May 7, 2024 8:47 PM To: StarlingX ML <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website. The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn. I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them? Thanks and Best Regards, Ildikó [1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf<https://urldefense.com/v3/__https:/www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf__;!!AjveYdw8EvQ!aLMbd-Zp0RAKZzHdz0vnKmY1M2kRSHpJH06E1lrlZLd3qht35WHnYBki8vau1htFnOr0K5qu29HNkrPP0Pz3_Qsg$> ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
Hi Ildiko, thanks for updating this slide deck! I have couple of comments regarding the stx-openstack slides: * Slide 28: Remove the Armada mention * Deployed using Helm (using OpenStack-Helm charts) and FluxCD (StarlingX default orchestrator for deploying Helm charts) * Slide 29: Remove services deprecated/no longer supported * Should remove: Barbican and Ironic from first item * Should remove the entire Telemetry item and subitems Apart from that, I have some thoughts on gradually enhancing the stx-openstack documentation and maybe on a future slide deck update we can add more information on our OpenStack distro. Thanks again. Thales Cervi ________________________________ From: Webster, Steven <Steven.Webster@windriver.com> Sent: Thursday, June 6, 2024 10:55 AM To: Ildiko Vancsa <ildiko@openinfra.dev>; Waines, Greg <Greg.Waines@windriver.com> Cc: StarlingX ML <starlingx-discuss@lists.starlingx.io>; Ngo, Tee <Tee.Ngo@windriver.com>; Reed, Joshua <Joshua.Reed@windriver.com> Subject: RE: Updating the overview slide deck Hey Ildiko thanks for taking this initiative and sorry for the slow response! I’ll leave comments to Greg’s questions inline marked with [> steve]:. From: Ildiko Vancsa <ildiko@openinfra.dev> Sent: Wednesday, May 22, 2024 12:46 AM To: Waines, Greg <Greg.Waines@windriver.com> Cc: StarlingX ML <starlingx-discuss@lists.starlingx.io>; Ngo, Tee <Tee.Ngo@windriver.com>; Webster, Steven <Steven.Webster@windriver.com>; Reed, Joshua <Joshua.Reed@windriver.com> Subject: Re: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks Greg for your input! I will wait for responses from people you tagged, as well as any further comments before starting to edit the slide deck. Does anyone have further comments on what needs to be updated in the StarlingX overview slide deck? Best Regards, Ildikó ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation On May 16, 2024, at 5:00 AM, Waines, Greg <Greg.Waines@windriver.com<mailto:Greg.Waines@windriver.com>> wrote: Hey Ildiko, I took a look at the StarlingX Overview Slide Deck. ( NOTE … I have questions for @Ngo, Tee<mailto:Tee.Ngo@windriver.com>, @Webster, Steven<mailto:Steven.Webster@windriver.com>, @Reed, Joshua<mailto:Joshua.Reed@windriver.com> … below. ) Some ideas on updates that could be done: * Add Geo-Redundancy of Central Cloud in Distributed Cloud configurations * SLIDE 6 * @Ngo, Tee<mailto:Tee.Ngo@windriver.com> do you have a Geo-Redundancy diagram that you could share with Ildiko ? * SLIDE 9 - StarlingX - Edge Virtualization Platform * i.e. very very high-level software architecture diagram * changes ? * under OpenStack Components * remove ‘Bare Metal’ and ‘Object Storage’ blocks * they are not supported * under Kubernetes Components * I would change ‘DNS Service’ to ‘Core DNS’ … I believe that is what it is referring to,@Webster, Steven<mailto:Steven.Webster@windriver.com> ? and [> steve]: I think that’s fine ^ * What is Network Proxy referring to ? CNI ? [> steve]: Yeah this is kind of a weird one. I think it would be much better referred to as you say below by “CNI”. Should we just change that to ‘CNI’ or ‘Container Networking’ ? @Webster, Steven<mailto:Steven.Webster@windriver.com> ? [> steve]: I think “CNI” is fine to keep as it’s commonly used in the community and it probably makes it easier to fit on the diagram. * We should similarly add ‘CSI’ or ‘Container Storage’ * We should change ‘Helm’ to ‘FluxCD, Helm’ * We should change ‘Dashboard’ to ‘Kubectl , Dashboard’ * I would add a block for ‘Integrated OpenSource Container Services’ * i.e. for all the open-source containerized services that we integrate into solution * e.g. nginx, cert-manager, metrics server, istio, vault, dex, kubevirt, security profiles operator, portieris, etc. * for the layer just above Linux * Remove Armada * For the Linux Layer * change to ‘Linux - Debian’ ? * SLIDE 10 * Change the ‘Kubernetes + OpenStack’ block to just ‘Kubernetes’ * OpenStack is in the Containerized block above it * SLIDE 11 * For the ORANGE layer * Remove ‘TPM’ block … not supported anymore * we have plans to add it back in … but not sure when that will happen * For the GREEN layer * Change ‘Low Latency Linux’ * to: ‘Standard or Low Latency Linux - Debian’ * SLIDE 12 * For scalability bullet … should replace with something like * Scalable deployment models * For Standalone Cloud * Support 1-200 k8s workers * Support 1-10 k8s workers configured as OpenStack computes ( maybe don’t say this one … its embarrassing 😉 ) * For Distributed Cloud * Support 1-1,000 Subclouds * where each Subcloud is a cloud of 1-200 k8s workers * The bullet on “Focus on minimizing the infrastructure footprint” is not well written … not understandable Suggested REWORD * Minimize infrastructure footprint / overhead * For Standard (Controllers + Workers) Configuration * support 2-server controller/master solution * on worker nodes, only 1 core required for StarlingX Platform * For All-In-One (AIO) Configurations (i.e. AIO-Simplex and AIO-Duplex) * AIO servers require only 2 cores for StarlingX Platform * SLIDE 20 “Kubernetes Cluster Software Components” * Change Armada to FluxCD * Personally I would change ‘Ingress LB’ to ‘Nginx’ … to avoid any confusion * I would remove the current and future stuff * SLIDE 26 “Application Management” * Need to change the Armada stuff to FluxCD * @Reed, Joshua<mailto:Joshua.Reed@windriver.com> ? Could you provide updated text and diagram for this slide ? * SLIDE 29 Supported OpenStack Servies * Should remove * Ironic and Telemetry(Ceilometer Gnocchi Panko Aodh) * … not currently supported. * SLIDE 32 & 33 … on Distributed Cloud * @Ngo, Tee<mailto:Tee.Ngo@windriver.com> ? can you provide updated text for these two slides … and diagram if you feel its required Greg. From: Ildiko Vancsa <ildiko@openinfra.dev<mailto:ildiko@openinfra.dev>> Sent: Tuesday, May 7, 2024 8:47 PM To: StarlingX ML <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website. The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn. I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them? Thanks and Best Regards, Ildikó [1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf<https://urldefense.com/v3/__https:/www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf__;!!AjveYdw8EvQ!aLMbd-Zp0RAKZzHdz0vnKmY1M2kRSHpJH06E1lrlZLd3qht35WHnYBki8vau1htFnOr0K5qu29HNkrPP0Pz3_Qsg$> ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
Hi Thales, Great, thank you for your clarifications and input. Best Regards, Ildikó ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
On Jun 12, 2024, at 1:36 PM, Cervi, Thales Elero <ThalesElero.Cervi@windriver.com> wrote:
Hi Ildiko, thanks for updating this slide deck!
I have couple of comments regarding the stx-openstack slides: • Slide 28: Remove the Armada mention • Deployed using Helm (using OpenStack-Helm charts) and FluxCD (StarlingX default orchestrator for deploying Helm charts) • Slide 29: Remove services deprecated/no longer supported • Should remove: Barbican and Ironic from first item • Should remove the entire Telemetry item and subitems
Apart from that, I have some thoughts on gradually enhancing the stx-openstack documentation and maybe on a future slide deck update we can add more information on our OpenStack distro.
Thanks again. Thales CerviFrom: Webster, Steven <Steven.Webster@windriver.com> Sent: Thursday, June 6, 2024 10:55 AM To: Ildiko Vancsa <ildiko@openinfra.dev>; Waines, Greg <Greg.Waines@windriver.com> Cc: StarlingX ML <starlingx-discuss@lists.starlingx.io>; Ngo, Tee <Tee.Ngo@windriver.com>; Reed, Joshua <Joshua.Reed@windriver.com> Subject: RE: Updating the overview slide deck Hey Ildiko thanks for taking this initiative and sorry for the slow response! I’ll leave comments to Greg’s questions inline marked with [> steve]:. From: Ildiko Vancsa <ildiko@openinfra.dev> Sent: Wednesday, May 22, 2024 12:46 AM To: Waines, Greg <Greg.Waines@windriver.com> Cc: StarlingX ML <starlingx-discuss@lists.starlingx.io>; Ngo, Tee <Tee.Ngo@windriver.com>; Webster, Steven <Steven.Webster@windriver.com>; Reed, Joshua <Joshua.Reed@windriver.com> Subject: Re: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks Greg for your input! I will wait for responses from people you tagged, as well as any further comments before starting to edit the slide deck. Does anyone have further comments on what needs to be updated in the StarlingX overview slide deck? Best Regards, Ildikó ———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
On May 16, 2024, at 5:00 AM, Waines, Greg <Greg.Waines@windriver.com> wrote: Hey Ildiko, I took a look at the StarlingX Overview Slide Deck. ( NOTE … I have questions for @Ngo, Tee, @Webster, Steven, @Reed, Joshua … below. ) Some ideas on updates that could be done: • Add Geo-Redundancy of Central Cloud in Distributed Cloud configurations • SLIDE 6 • @Ngo, Tee do you have a Geo-Redundancy diagram that you could share with Ildiko ? • SLIDE 9 - StarlingX - Edge Virtualization Platform • i.e. very very high-level software architecture diagram • changes ? • under OpenStack Components • remove ‘Bare Metal’ and ‘Object Storage’ blocks • they are not supported • under Kubernetes Components • I would change ‘DNS Service’ to ‘Core DNS’ … I believe that is what it is referring to,@Webster, Steven ? and [> steve]: I think that’s fine ^ • What is Network Proxy referring to ? CNI ? [> steve]: Yeah this is kind of a weird one. I think it would be much better referred to as you say below by “CNI”. Should we just change that to ‘CNI’ or ‘Container Networking’ ? @Webster, Steven ? [> steve]: I think “CNI” is fine to keep as it’s commonly used in the community and it probably makes it easier to fit on the diagram. • We should similarly add ‘CSI’ or ‘Container Storage’ • We should change ‘Helm’ to ‘FluxCD, Helm’ • We should change ‘Dashboard’ to ‘Kubectl , Dashboard’ • I would add a block for ‘Integrated OpenSource Container Services’ • i.e. for all the open-source containerized services that we integrate into solution • e.g. nginx, cert-manager, metrics server, istio, vault, dex, kubevirt, security profiles operator, portieris, etc. • for the layer just above Linux • Remove Armada • For the Linux Layer • change to ‘Linux - Debian’ ? • SLIDE 10 • Change the ‘Kubernetes + OpenStack’ block to just ‘Kubernetes’ • OpenStack is in the Containerized block above it • SLIDE 11 • For the ORANGE layer • Remove ‘TPM’ block … not supported anymore • we have plans to add it back in … but not sure when that will happen • For the GREEN layer • Change ‘Low Latency Linux’ • to: ‘Standard or Low Latency Linux - Debian’ • SLIDE 12 • For scalability bullet … should replace with something like • Scalable deployment models • For Standalone Cloud • Support 1-200 k8s workers • Support 1-10 k8s workers configured as OpenStack computes ( maybe don’t say this one … its embarrassing 😉 ) • For Distributed Cloud • Support 1-1,000 Subclouds • where each Subcloud is a cloud of 1-200 k8s workers • The bullet on “Focus on minimizing the infrastructure footprint” is not well written … not understandable Suggested REWORD • Minimize infrastructure footprint / overhead • For Standard (Controllers + Workers) Configuration • support 2-server controller/master solution • on worker nodes, only 1 core required for StarlingX Platform • For All-In-One (AIO) Configurations (i.e. AIO-Simplex and AIO-Duplex) • AIO servers require only 2 cores for StarlingX Platform • SLIDE 20 “Kubernetes Cluster Software Components” • Change Armada to FluxCD • Personally I would change ‘Ingress LB’ to ‘Nginx’ … to avoid any confusion • I would remove the current and future stuff • SLIDE 26 “Application Management” • Need to change the Armada stuff to FluxCD • @Reed, Joshua ? Could you provide updated text and diagram for this slide ? • SLIDE 29 Supported OpenStack Servies • Should remove • Ironic and Telemetry(Ceilometer Gnocchi Panko Aodh) • … not currently supported. • SLIDE 32 & 33 … on Distributed Cloud • @Ngo, Tee ? can you provide updated text for these two slides … and diagram if you feel its required Greg. From: Ildiko Vancsa <ildiko@openinfra.dev> Sent: Tuesday, May 7, 2024 8:47 PM To: StarlingX ML <starlingx-discuss@lists.starlingx.io> Subject: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website. The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn. I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them? Thanks and Best Regards, Ildikó [1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf ———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
Hi All, Thank you for all the feedback on the StarlingX overview slide deck so far. I have a couple of quick questions: - If I remember correctly, Keystone and Horizon were used on the platform layer in the past. have they both been replaced since then? - The overview deck has a slide on each Flow Services component. Are those slides, including description and diagrams, still accurate? Thanks, Ildikó ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
On Jun 12, 2024, at 3:32 PM, Ildiko Vancsa <ildiko@openinfra.dev> wrote:
Hi Thales,
Great, thank you for your clarifications and input.
Best Regards, Ildikó
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
On Jun 12, 2024, at 1:36 PM, Cervi, Thales Elero <ThalesElero.Cervi@windriver.com> wrote:
Hi Ildiko, thanks for updating this slide deck!
I have couple of comments regarding the stx-openstack slides: • Slide 28: Remove the Armada mention • Deployed using Helm (using OpenStack-Helm charts) and FluxCD (StarlingX default orchestrator for deploying Helm charts) • Slide 29: Remove services deprecated/no longer supported • Should remove: Barbican and Ironic from first item • Should remove the entire Telemetry item and subitems
Apart from that, I have some thoughts on gradually enhancing the stx-openstack documentation and maybe on a future slide deck update we can add more information on our OpenStack distro.
Thanks again. Thales CerviFrom: Webster, Steven <Steven.Webster@windriver.com> Sent: Thursday, June 6, 2024 10:55 AM To: Ildiko Vancsa <ildiko@openinfra.dev>; Waines, Greg <Greg.Waines@windriver.com> Cc: StarlingX ML <starlingx-discuss@lists.starlingx.io>; Ngo, Tee <Tee.Ngo@windriver.com>; Reed, Joshua <Joshua.Reed@windriver.com> Subject: RE: Updating the overview slide deck Hey Ildiko thanks for taking this initiative and sorry for the slow response! I’ll leave comments to Greg’s questions inline marked with [> steve]:. From: Ildiko Vancsa <ildiko@openinfra.dev> Sent: Wednesday, May 22, 2024 12:46 AM To: Waines, Greg <Greg.Waines@windriver.com> Cc: StarlingX ML <starlingx-discuss@lists.starlingx.io>; Ngo, Tee <Tee.Ngo@windriver.com>; Webster, Steven <Steven.Webster@windriver.com>; Reed, Joshua <Joshua.Reed@windriver.com> Subject: Re: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks Greg for your input! I will wait for responses from people you tagged, as well as any further comments before starting to edit the slide deck. Does anyone have further comments on what needs to be updated in the StarlingX overview slide deck? Best Regards, Ildikó ———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
On May 16, 2024, at 5:00 AM, Waines, Greg <Greg.Waines@windriver.com> wrote: Hey Ildiko, I took a look at the StarlingX Overview Slide Deck. ( NOTE … I have questions for @Ngo, Tee, @Webster, Steven, @Reed, Joshua … below. ) Some ideas on updates that could be done: • Add Geo-Redundancy of Central Cloud in Distributed Cloud configurations • SLIDE 6 • @Ngo, Tee do you have a Geo-Redundancy diagram that you could share with Ildiko ? • SLIDE 9 - StarlingX - Edge Virtualization Platform • i.e. very very high-level software architecture diagram • changes ? • under OpenStack Components • remove ‘Bare Metal’ and ‘Object Storage’ blocks • they are not supported • under Kubernetes Components • I would change ‘DNS Service’ to ‘Core DNS’ … I believe that is what it is referring to,@Webster, Steven ? and [> steve]: I think that’s fine ^ • What is Network Proxy referring to ? CNI ? [> steve]: Yeah this is kind of a weird one. I think it would be much better referred to as you say below by “CNI”. Should we just change that to ‘CNI’ or ‘Container Networking’ ? @Webster, Steven ? [> steve]: I think “CNI” is fine to keep as it’s commonly used in the community and it probably makes it easier to fit on the diagram. • We should similarly add ‘CSI’ or ‘Container Storage’ • We should change ‘Helm’ to ‘FluxCD, Helm’ • We should change ‘Dashboard’ to ‘Kubectl , Dashboard’ • I would add a block for ‘Integrated OpenSource Container Services’ • i.e. for all the open-source containerized services that we integrate into solution • e.g. nginx, cert-manager, metrics server, istio, vault, dex, kubevirt, security profiles operator, portieris, etc. • for the layer just above Linux • Remove Armada • For the Linux Layer • change to ‘Linux - Debian’ ? • SLIDE 10 • Change the ‘Kubernetes + OpenStack’ block to just ‘Kubernetes’ • OpenStack is in the Containerized block above it • SLIDE 11 • For the ORANGE layer • Remove ‘TPM’ block … not supported anymore • we have plans to add it back in … but not sure when that will happen • For the GREEN layer • Change ‘Low Latency Linux’ • to: ‘Standard or Low Latency Linux - Debian’ • SLIDE 12 • For scalability bullet … should replace with something like • Scalable deployment models • For Standalone Cloud • Support 1-200 k8s workers • Support 1-10 k8s workers configured as OpenStack computes ( maybe don’t say this one … its embarrassing 😉 ) • For Distributed Cloud • Support 1-1,000 Subclouds • where each Subcloud is a cloud of 1-200 k8s workers • The bullet on “Focus on minimizing the infrastructure footprint” is not well written … not understandable Suggested REWORD • Minimize infrastructure footprint / overhead • For Standard (Controllers + Workers) Configuration • support 2-server controller/master solution • on worker nodes, only 1 core required for StarlingX Platform • For All-In-One (AIO) Configurations (i.e. AIO-Simplex and AIO-Duplex) • AIO servers require only 2 cores for StarlingX Platform • SLIDE 20 “Kubernetes Cluster Software Components” • Change Armada to FluxCD • Personally I would change ‘Ingress LB’ to ‘Nginx’ … to avoid any confusion • I would remove the current and future stuff • SLIDE 26 “Application Management” • Need to change the Armada stuff to FluxCD • @Reed, Joshua ? Could you provide updated text and diagram for this slide ? • SLIDE 29 Supported OpenStack Servies • Should remove • Ironic and Telemetry(Ceilometer Gnocchi Panko Aodh) • … not currently supported. • SLIDE 32 & 33 … on Distributed Cloud • @Ngo, Tee ? can you provide updated text for these two slides … and diagram if you feel its required Greg. From: Ildiko Vancsa <ildiko@openinfra.dev> Sent: Tuesday, May 7, 2024 8:47 PM To: StarlingX ML <starlingx-discuss@lists.starlingx.io> Subject: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website. The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn. I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them? Thanks and Best Regards, Ildikó [1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf ———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
See in-lined below, Greg. -----Original Message----- From: Ildiko Vancsa <ildiko@openinfra.dev> Sent: Wednesday, June 12, 2024 6:35 PM To: StarlingX ML <starlingx-discuss@lists.starlingx.io> Cc: Cervi, Thales Elero <ThalesElero.Cervi@windriver.com>; Webster, Steven <Steven.Webster@windriver.com>; Waines, Greg <Greg.Waines@windriver.com>; Ngo, Tee <Tee.Ngo@windriver.com> Subject: Re: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi All, Thank you for all the feedback on the StarlingX overview slide deck so far. I have a couple of quick questions: - If I remember correctly, Keystone and Horizon were used on the platform layer in the past. have they both been replaced since then? [Greg] Keystone, Barbican and Horizon are still used in the Platform layer. - The overview deck has a slide on each Flow Services component. Are those slides, including description and diagrams, still accurate? [Greg] Yes, the Flock Services component slides are still accurate. Greg. Thanks, Ildikó ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
On Jun 12, 2024, at 3:32 PM, Ildiko Vancsa <ildiko@openinfra.dev<mailto:ildiko@openinfra.dev>> wrote:
Hi Thales,
Great, thank you for your clarifications and input.
Best Regards, Ildikó
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
On Jun 12, 2024, at 1:36 PM, Cervi, Thales Elero <ThalesElero.Cervi@windriver.com<mailto:ThalesElero.Cervi@windriver.com>> wrote:
Hi Ildiko, thanks for updating this slide deck!
I have couple of comments regarding the stx-openstack slides: • Slide 28: Remove the Armada mention • Deployed using Helm (using OpenStack-Helm charts) and FluxCD (StarlingX default orchestrator for deploying Helm charts) • Slide 29: Remove services deprecated/no longer supported • Should remove: Barbican and Ironic from first item • Should remove the entire Telemetry item and subitems
Apart from that, I have some thoughts on gradually enhancing the stx-openstack documentation and maybe on a future slide deck update we can add more information on our OpenStack distro.
Thanks again. Thales CerviFrom: Webster, Steven <Steven.Webster@windriver.com<mailto:Steven.Webster@windriver.com>> Sent: Thursday, June 6, 2024 10:55 AM To: Ildiko Vancsa <ildiko@openinfra.dev<mailto:ildiko@openinfra.dev>>; Waines, Greg <Greg.Waines@windriver.com<mailto:Greg.Waines@windriver.com>> Cc: StarlingX ML <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>>; Ngo, Tee <Tee.Ngo@windriver.com<mailto:Tee.Ngo@windriver.com>>; Reed, Joshua <Joshua.Reed@windriver.com<mailto:Joshua.Reed@windriver.com>> Subject: RE: Updating the overview slide deck Hey Ildiko thanks for taking this initiative and sorry for the slow response! I’ll leave comments to Greg’s questions inline marked with [> steve]:. From: Ildiko Vancsa <ildiko@openinfra.dev<mailto:ildiko@openinfra.dev>> Sent: Wednesday, May 22, 2024 12:46 AM To: Waines, Greg <Greg.Waines@windriver.com<mailto:Greg.Waines@windriver.com>> Cc: StarlingX ML <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>>; Ngo, Tee <Tee.Ngo@windriver.com<mailto:Tee.Ngo@windriver.com>>; Webster, Steven <Steven.Webster@windriver.com<mailto:Steven.Webster@windriver.com>>; Reed, Joshua <Joshua.Reed@windriver.com<mailto:Joshua.Reed@windriver.com>> Subject: Re: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks Greg for your input! I will wait for responses from people you tagged, as well as any further comments before starting to edit the slide deck. Does anyone have further comments on what needs to be updated in the StarlingX overview slide deck? Best Regards, Ildikó ———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
On May 16, 2024, at 5:00 AM, Waines, Greg <Greg.Waines@windriver.com<mailto:Greg.Waines@windriver.com>> wrote: Hey Ildiko, I took a look at the StarlingX Overview Slide Deck. ( NOTE … I have questions for @Ngo, Tee, @Webster, Steven, @Reed, Joshua … below. ) Some ideas on updates that could be done: • Add Geo-Redundancy of Central Cloud in Distributed Cloud configurations • SLIDE 6 • @Ngo, Tee do you have a Geo-Redundancy diagram that you could share with Ildiko ? • SLIDE 9 - StarlingX - Edge Virtualization Platform • i.e. very very high-level software architecture diagram • changes ? • under OpenStack Components • remove ‘Bare Metal’ and ‘Object Storage’ blocks • they are not supported • under Kubernetes Components • I would change ‘DNS Service’ to ‘Core DNS’ … I believe that is what it is referring to,@Webster, Steven ? and [> steve]: I think that’s fine ^ • What is Network Proxy referring to ? CNI ? [> steve]: Yeah this is kind of a weird one. I think it would be much better referred to as you say below by “CNI”. Should we just change that to ‘CNI’ or ‘Container Networking’ ? @Webster, Steven ? [> steve]: I think “CNI” is fine to keep as it’s commonly used in the community and it probably makes it easier to fit on the diagram. • We should similarly add ‘CSI’ or ‘Container Storage’ • We should change ‘Helm’ to ‘FluxCD, Helm’ • We should change ‘Dashboard’ to ‘Kubectl , Dashboard’ • I would add a block for ‘Integrated OpenSource Container Services’ • i.e. for all the open-source containerized services that we integrate into solution • e.g. nginx, cert-manager, metrics server, istio, vault, dex, kubevirt, security profiles operator, portieris, etc. • for the layer just above Linux • Remove Armada • For the Linux Layer • change to ‘Linux - Debian’ ? • SLIDE 10 • Change the ‘Kubernetes + OpenStack’ block to just ‘Kubernetes’ • OpenStack is in the Containerized block above it • SLIDE 11 • For the ORANGE layer • Remove ‘TPM’ block … not supported anymore • we have plans to add it back in … but not sure when that will happen • For the GREEN layer • Change ‘Low Latency Linux’ • to: ‘Standard or Low Latency Linux - Debian’ • SLIDE 12 • For scalability bullet … should replace with something like • Scalable deployment models • For Standalone Cloud • Support 1-200 k8s workers • Support 1-10 k8s workers configured as OpenStack computes ( maybe don’t say this one … its embarrassing 😉 ) • For Distributed Cloud • Support 1-1,000 Subclouds • where each Subcloud is a cloud of 1-200 k8s workers • The bullet on “Focus on minimizing the infrastructure footprint” is not well written … not understandable Suggested REWORD • Minimize infrastructure footprint / overhead • For Standard (Controllers + Workers) Configuration • support 2-server controller/master solution • on worker nodes, only 1 core required for StarlingX Platform • For All-In-One (AIO) Configurations (i.e. AIO-Simplex and AIO-Duplex) • AIO servers require only 2 cores for StarlingX Platform • SLIDE 20 “Kubernetes Cluster Software Components” • Change Armada to FluxCD • Personally I would change ‘Ingress LB’ to ‘Nginx’ … to avoid any confusion • I would remove the current and future stuff • SLIDE 26 “Application Management” • Need to change the Armada stuff to FluxCD • @Reed, Joshua ? Could you provide updated text and diagram for this slide ? • SLIDE 29 Supported OpenStack Servies • Should remove • Ironic and Telemetry(Ceilometer Gnocchi Panko Aodh) • … not currently supported. • SLIDE 32 & 33 … on Distributed Cloud • @Ngo, Tee ? can you provide updated text for these two slides … and diagram if you feel its required Greg. From: Ildiko Vancsa <ildiko@openinfra.dev<mailto:ildiko@openinfra.dev>> Sent: Tuesday, May 7, 2024 8:47 PM To: StarlingX ML <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website. The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn. I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them? Thanks and Best Regards, Ildikó [1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web .pdf ———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
Hi Steven, Thank you for the clarifications. Best Regards, Ildikó ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
On Jun 6, 2024, at 6:55 AM, Webster, Steven <Steven.Webster@windriver.com> wrote:
Hey Ildiko thanks for taking this initiative and sorry for the slow response! I’ll leave comments to Greg’s questions inline marked with [> steve]:. From: Ildiko Vancsa <ildiko@openinfra.dev> Sent: Wednesday, May 22, 2024 12:46 AM To: Waines, Greg <Greg.Waines@windriver.com> Cc: StarlingX ML <starlingx-discuss@lists.starlingx.io>; Ngo, Tee <Tee.Ngo@windriver.com>; Webster, Steven <Steven.Webster@windriver.com>; Reed, Joshua <Joshua.Reed@windriver.com> Subject: Re: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Thanks Greg for your input! I will wait for responses from people you tagged, as well as any further comments before starting to edit the slide deck. Does anyone have further comments on what needs to be updated in the StarlingX overview slide deck? Best Regards, Ildikó ———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
On May 16, 2024, at 5:00 AM, Waines, Greg <Greg.Waines@windriver.com> wrote: Hey Ildiko, I took a look at the StarlingX Overview Slide Deck. ( NOTE … I have questions for @Ngo, Tee, @Webster, Steven, @Reed, Joshua … below. ) Some ideas on updates that could be done: • Add Geo-Redundancy of Central Cloud in Distributed Cloud configurations • SLIDE 6 • @Ngo, Tee do you have a Geo-Redundancy diagram that you could share with Ildiko ? • SLIDE 9 - StarlingX - Edge Virtualization Platform • i.e. very very high-level software architecture diagram • changes ? • under OpenStack Components • remove ‘Bare Metal’ and ‘Object Storage’ blocks • they are not supported • under Kubernetes Components • I would change ‘DNS Service’ to ‘Core DNS’ … I believe that is what it is referring to,@Webster, Steven ? and [> steve]: I think that’s fine ^ • What is Network Proxy referring to ? CNI ? [> steve]: Yeah this is kind of a weird one. I think it would be much better referred to as you say below by “CNI”. Should we just change that to ‘CNI’ or ‘Container Networking’ ? @Webster, Steven ? [> steve]: I think “CNI” is fine to keep as it’s commonly used in the community and it probably makes it easier to fit on the diagram. • We should similarly add ‘CSI’ or ‘Container Storage’ • We should change ‘Helm’ to ‘FluxCD, Helm’ • We should change ‘Dashboard’ to ‘Kubectl , Dashboard’ • I would add a block for ‘Integrated OpenSource Container Services’ • i.e. for all the open-source containerized services that we integrate into solution • e.g. nginx, cert-manager, metrics server, istio, vault, dex, kubevirt, security profiles operator, portieris, etc. • for the layer just above Linux • Remove Armada • For the Linux Layer • change to ‘Linux - Debian’ ? • SLIDE 10 • Change the ‘Kubernetes + OpenStack’ block to just ‘Kubernetes’ • OpenStack is in the Containerized block above it • SLIDE 11 • For the ORANGE layer • Remove ‘TPM’ block … not supported anymore • we have plans to add it back in … but not sure when that will happen • For the GREEN layer • Change ‘Low Latency Linux’ • to: ‘Standard or Low Latency Linux - Debian’ • SLIDE 12 • For scalability bullet … should replace with something like • Scalable deployment models • For Standalone Cloud • Support 1-200 k8s workers • Support 1-10 k8s workers configured as OpenStack computes ( maybe don’t say this one … its embarrassing 😉 ) • For Distributed Cloud • Support 1-1,000 Subclouds • where each Subcloud is a cloud of 1-200 k8s workers • The bullet on “Focus on minimizing the infrastructure footprint” is not well written … not understandable Suggested REWORD • Minimize infrastructure footprint / overhead • For Standard (Controllers + Workers) Configuration • support 2-server controller/master solution • on worker nodes, only 1 core required for StarlingX Platform • For All-In-One (AIO) Configurations (i.e. AIO-Simplex and AIO-Duplex) • AIO servers require only 2 cores for StarlingX Platform • SLIDE 20 “Kubernetes Cluster Software Components” • Change Armada to FluxCD • Personally I would change ‘Ingress LB’ to ‘Nginx’ … to avoid any confusion • I would remove the current and future stuff • SLIDE 26 “Application Management” • Need to change the Armada stuff to FluxCD • @Reed, Joshua ? Could you provide updated text and diagram for this slide ? • SLIDE 29 Supported OpenStack Servies • Should remove • Ironic and Telemetry(Ceilometer Gnocchi Panko Aodh) • … not currently supported. • SLIDE 32 & 33 … on Distributed Cloud • @Ngo, Tee ? can you provide updated text for these two slides … and diagram if you feel its required Greg. From: Ildiko Vancsa <ildiko@openinfra.dev> Sent: Tuesday, May 7, 2024 8:47 PM To: StarlingX ML <starlingx-discuss@lists.starlingx.io> Subject: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website. The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn. I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them? Thanks and Best Regards, Ildikó [1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf ———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
I added some additional info below, Greg. From: Waines, Greg Sent: Thursday, May 16, 2024 8:00 AM To: Ildiko Vancsa <ildiko@openinfra.dev>; StarlingX ML <starlingx-discuss@lists.starlingx.io> Cc: Ngo, Tee <Tee.Ngo@windriver.com>; Webster, Steven <Steven.Webster@windriver.com>; Reed, Joshua <Joshua.Reed@windriver.com> Subject: RE: Updating the overview slide deck Hey Ildiko, I took a look at the StarlingX Overview Slide Deck. ( NOTE … I have questions for @Ngo, Tee<mailto:Tee.Ngo@windriver.com>, @Webster, Steven<mailto:Steven.Webster@windriver.com>, @Reed, Joshua<mailto:Joshua.Reed@windriver.com> … below. ) Some ideas on updates that could be done: * Add Geo-Redundancy of Central Cloud in Distributed Cloud configurations * SLIDE 6 * @Ngo, Tee<mailto:Tee.Ngo@windriver.com> do you have a Geo-Redundancy diagram that you could share with Ildiko ? * [Greg] See attached proposed new slide, ‘updated-DC-Diagram.pptx’ * SLIDE 9 - StarlingX - Edge Virtualization Platform * i.e. very very high-level software architecture diagram * changes ? * under OpenStack Components * remove ‘Bare Metal’ and ‘Object Storage’ blocks * they are not supported * under Kubernetes Components * I would change ‘DNS Service’ to ‘Core DNS’ … I believe that is what it is referring to, @Webster, Steven<mailto:Steven.Webster@windriver.com> ? and * What is Network Proxy referring to ? CNI ? Should we just change that to ‘CNI’ or ‘Container Networking’ ? @Webster, Steven<mailto:Steven.Webster@windriver.com> ? * We should similarly add ‘CSI’ or ‘Container Storage’ * We should change ‘Helm’ to ‘FluxCD, Helm’ * We should change ‘Dashboard’ to ‘Kubectl , Dashboard’ * I would add a block for ‘Integrated OpenSource Container Services’ * i.e. for all the open-source containerized services that we integrate into solution * e.g. nginx, cert-manager, metrics server, istio, vault, dex, kubevirt, security profiles operator, portieris, etc. * for the layer just above Linux * Remove Armada * For the Linux Layer * change to ‘Linux - Debian’ ? * SLIDE 10 * Change the ‘Kubernetes + OpenStack’ block to just ‘Kubernetes’ * OpenStack is in the Containerized block above it * SLIDE 11 * For the ORANGE layer * Remove ‘TPM’ block … not supported anymore * we have plans to add it back in … but not sure when that will happen * For the GREEN layer * Change ‘Low Latency Linux’ * to: ‘Standard or Low Latency Linux - Debian’ * SLIDE 12 * For scalability bullet … should replace with something like * Scalable deployment models * For Standalone Cloud * Support 1-200 k8s workers * Support 1-10 k8s workers configured as OpenStack computes ( maybe don’t say this one … its embarrassing 😉 ) * For Distributed Cloud * Support 1-1,000 Subclouds * where each Subcloud is a cloud of 1-200 k8s workers * The bullet on “Focus on minimizing the infrastructure footprint” is not well written … not understandable Suggested REWORD * Minimize infrastructure footprint / overhead * For Standard (Controllers + Workers) Configuration * support 2-server controller/master solution * on worker nodes, only 1 core required for StarlingX Platform * For All-In-One (AIO) Configurations (i.e. AIO-Simplex and AIO-Duplex) * AIO servers require only 2 cores for StarlingX Platform * SLIDE 20 “Kubernetes Cluster Software Components” * Change Armada to FluxCD * Personally I would change ‘Ingress LB’ to ‘Nginx’ … to avoid any confusion * I would remove the current and future stuff * SLIDE 26 “Application Management” * Need to change the Armada stuff to FluxCD * @Reed, Joshua<mailto:Joshua.Reed@windriver.com> ? Could you provide updated text and diagram for this slide ? * [Greg] See attached proposed new slide, ‘updated-App-Mgmt-slides-Copy.pptx’ * SLIDE 29 Supported OpenStack Servies * Should remove * Ironic and Telemetry(Ceilometer Gnocchi Panko Aodh) * … not currently supported. * SLIDE 32 & 33 … on Distributed Cloud * @Ngo, Tee<mailto:Tee.Ngo@windriver.com> ? can you provide updated text for these two slides … and diagram if you feel its required * [Greg] See attached proposed new slides, ‘updated-DC-Slides.pptx’ Greg. From: Ildiko Vancsa <ildiko@openinfra.dev<mailto:ildiko@openinfra.dev>> Sent: Tuesday, May 7, 2024 8:47 PM To: StarlingX ML <starlingx-discuss@lists.starlingx.io<mailto:starlingx-discuss@lists.starlingx.io>> Subject: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website. The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn. I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them? Thanks and Best Regards, Ildikó [1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf<https://urldefense.com/v3/__https:/www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf__;!!AjveYdw8EvQ!aLMbd-Zp0RAKZzHdz0vnKmY1M2kRSHpJH06E1lrlZLd3qht35WHnYBki8vau1htFnOr0K5qu29HNkrPP0Pz3_Qsg$> ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
Perfect, thanks Greg! ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
On Jun 13, 2024, at 11:54 AM, Waines, Greg <Greg.Waines@windriver.com> wrote:
I added some additional info below, Greg. From: Waines, Greg Sent: Thursday, May 16, 2024 8:00 AM To: Ildiko Vancsa <ildiko@openinfra.dev>; StarlingX ML <starlingx-discuss@lists.starlingx.io> Cc: Ngo, Tee <Tee.Ngo@windriver.com>; Webster, Steven <Steven.Webster@windriver.com>; Reed, Joshua <Joshua.Reed@windriver.com> Subject: RE: Updating the overview slide deck Hey Ildiko, I took a look at the StarlingX Overview Slide Deck. ( NOTE … I have questions for @Ngo, Tee, @Webster, Steven, @Reed, Joshua … below. ) Some ideas on updates that could be done: • Add Geo-Redundancy of Central Cloud in Distributed Cloud configurations • SLIDE 6 • @Ngo, Tee do you have a Geo-Redundancy diagram that you could share with Ildiko ? • [Greg] See attached proposed new slide, ‘updated-DC-Diagram.pptx’
• SLIDE 9 - StarlingX - Edge Virtualization Platform • i.e. very very high-level software architecture diagram • changes ? • under OpenStack Components • remove ‘Bare Metal’ and ‘Object Storage’ blocks • they are not supported • under Kubernetes Components • I would change ‘DNS Service’ to ‘Core DNS’ … I believe that is what it is referring to,@Webster, Steven ? and • What is Network Proxy referring to ? CNI ? Should we just change that to ‘CNI’ or ‘Container Networking’ ? @Webster, Steven ? • We should similarly add ‘CSI’ or ‘Container Storage’ • We should change ‘Helm’ to ‘FluxCD, Helm’ • We should change ‘Dashboard’ to ‘Kubectl , Dashboard’ • I would add a block for ‘Integrated OpenSource Container Services’ • i.e. for all the open-source containerized services that we integrate into solution • e.g. nginx, cert-manager, metrics server, istio, vault, dex, kubevirt, security profiles operator, portieris, etc. • for the layer just above Linux • Remove Armada • For the Linux Layer • change to ‘Linux - Debian’ ? • SLIDE 10 • Change the ‘Kubernetes + OpenStack’ block to just ‘Kubernetes’ • OpenStack is in the Containerized block above it • SLIDE 11 • For the ORANGE layer • Remove ‘TPM’ block … not supported anymore • we have plans to add it back in … but not sure when that will happen • For the GREEN layer • Change ‘Low Latency Linux’ • to: ‘Standard or Low Latency Linux - Debian’ • SLIDE 12 • For scalability bullet … should replace with something like • Scalable deployment models • For Standalone Cloud • Support 1-200 k8s workers • Support 1-10 k8s workers configured as OpenStack computes ( maybe don’t say this one … its embarrassing 😉 ) • For Distributed Cloud • Support 1-1,000 Subclouds • where each Subcloud is a cloud of 1-200 k8s workers • The bullet on “Focus on minimizing the infrastructure footprint” is not well written … not understandable Suggested REWORD • Minimize infrastructure footprint / overhead • For Standard (Controllers + Workers) Configuration • support 2-server controller/master solution • on worker nodes, only 1 core required for StarlingX Platform • For All-In-One (AIO) Configurations (i.e. AIO-Simplex and AIO-Duplex) • AIO servers require only 2 cores for StarlingX Platform • SLIDE 20 “Kubernetes Cluster Software Components” • Change Armada to FluxCD • Personally I would change ‘Ingress LB’ to ‘Nginx’ … to avoid any confusion • I would remove the current and future stuff • SLIDE 26 “Application Management” • Need to change the Armada stuff to FluxCD • @Reed, Joshua ? Could you provide updated text and diagram for this slide ? • [Greg] See attached proposed new slide, ‘updated-App-Mgmt-slides-Copy.pptx’ • SLIDE 29 Supported OpenStack Servies • Should remove • Ironic and Telemetry(Ceilometer Gnocchi Panko Aodh) • … not currently supported. • SLIDE 32 & 33 … on Distributed Cloud • @Ngo, Tee ? can you provide updated text for these two slides … and diagram if you feel its required • [Greg] See attached proposed new slides, ‘updated-DC-Slides.pptx’
Greg. From: Ildiko Vancsa <ildiko@openinfra.dev> Sent: Tuesday, May 7, 2024 8:47 PM To: StarlingX ML <starlingx-discuss@lists.starlingx.io> Subject: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website. The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn. I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them? Thanks and Best Regards, Ildikó [1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf ———
Ildikó Váncsa Director of Community Open Infrastructure Foundation <updated-DC-Diagram.pptx><updated-DC-Slides.pptx><updated-App-Mgmt-Slides - Copy.pptx>
Hi All, I applied the changes y’all suggested to the deck so far, I’m currently waiting for our design team to finalize the updates to 2 of the diagrams. Once those diagrams are available, I will create a review to upload the new version to make it available in the docs repo. When that change gets merged, I will also update a new PDF version to the project’s website. Please let me know if there are any further updates you would like to make to the slides in the meantime. Thanks and Best Regards, Ildikó ——— Ildikó Váncsa Director of Community Open Infrastructure Foundation
On Jun 13, 2024, at 4:07 PM, Ildiko Vancsa <ildiko@openinfra.dev> wrote:
Perfect, thanks Greg!
———
Ildikó Váncsa Director of Community Open Infrastructure Foundation
On Jun 13, 2024, at 11:54 AM, Waines, Greg <Greg.Waines@windriver.com> wrote:
I added some additional info below, Greg. From: Waines, Greg Sent: Thursday, May 16, 2024 8:00 AM To: Ildiko Vancsa <ildiko@openinfra.dev>; StarlingX ML <starlingx-discuss@lists.starlingx.io> Cc: Ngo, Tee <Tee.Ngo@windriver.com>; Webster, Steven <Steven.Webster@windriver.com>; Reed, Joshua <Joshua.Reed@windriver.com> Subject: RE: Updating the overview slide deck Hey Ildiko, I took a look at the StarlingX Overview Slide Deck. ( NOTE … I have questions for @Ngo, Tee, @Webster, Steven, @Reed, Joshua … below. ) Some ideas on updates that could be done: • Add Geo-Redundancy of Central Cloud in Distributed Cloud configurations • SLIDE 6 • @Ngo, Tee do you have a Geo-Redundancy diagram that you could share with Ildiko ? • [Greg] See attached proposed new slide, ‘updated-DC-Diagram.pptx’
• SLIDE 9 - StarlingX - Edge Virtualization Platform • i.e. very very high-level software architecture diagram • changes ? • under OpenStack Components • remove ‘Bare Metal’ and ‘Object Storage’ blocks • they are not supported • under Kubernetes Components • I would change ‘DNS Service’ to ‘Core DNS’ … I believe that is what it is referring to,@Webster, Steven ? and • What is Network Proxy referring to ? CNI ? Should we just change that to ‘CNI’ or ‘Container Networking’ ? @Webster, Steven ? • We should similarly add ‘CSI’ or ‘Container Storage’ • We should change ‘Helm’ to ‘FluxCD, Helm’ • We should change ‘Dashboard’ to ‘Kubectl , Dashboard’ • I would add a block for ‘Integrated OpenSource Container Services’ • i.e. for all the open-source containerized services that we integrate into solution • e.g. nginx, cert-manager, metrics server, istio, vault, dex, kubevirt, security profiles operator, portieris, etc. • for the layer just above Linux • Remove Armada • For the Linux Layer • change to ‘Linux - Debian’ ? • SLIDE 10 • Change the ‘Kubernetes + OpenStack’ block to just ‘Kubernetes’ • OpenStack is in the Containerized block above it • SLIDE 11 • For the ORANGE layer • Remove ‘TPM’ block … not supported anymore • we have plans to add it back in … but not sure when that will happen • For the GREEN layer • Change ‘Low Latency Linux’ • to: ‘Standard or Low Latency Linux - Debian’ • SLIDE 12 • For scalability bullet … should replace with something like • Scalable deployment models • For Standalone Cloud • Support 1-200 k8s workers • Support 1-10 k8s workers configured as OpenStack computes ( maybe don’t say this one … its embarrassing 😉 ) • For Distributed Cloud • Support 1-1,000 Subclouds • where each Subcloud is a cloud of 1-200 k8s workers • The bullet on “Focus on minimizing the infrastructure footprint” is not well written … not understandable Suggested REWORD • Minimize infrastructure footprint / overhead • For Standard (Controllers + Workers) Configuration • support 2-server controller/master solution • on worker nodes, only 1 core required for StarlingX Platform • For All-In-One (AIO) Configurations (i.e. AIO-Simplex and AIO-Duplex) • AIO servers require only 2 cores for StarlingX Platform • SLIDE 20 “Kubernetes Cluster Software Components” • Change Armada to FluxCD • Personally I would change ‘Ingress LB’ to ‘Nginx’ … to avoid any confusion • I would remove the current and future stuff • SLIDE 26 “Application Management” • Need to change the Armada stuff to FluxCD • @Reed, Joshua ? Could you provide updated text and diagram for this slide ? • [Greg] See attached proposed new slide, ‘updated-App-Mgmt-slides-Copy.pptx’ • SLIDE 29 Supported OpenStack Servies • Should remove • Ironic and Telemetry(Ceilometer Gnocchi Panko Aodh) • … not currently supported. • SLIDE 32 & 33 … on Distributed Cloud • @Ngo, Tee ? can you provide updated text for these two slides … and diagram if you feel its required • [Greg] See attached proposed new slides, ‘updated-DC-Slides.pptx’
Greg. From: Ildiko Vancsa <ildiko@openinfra.dev> Sent: Tuesday, May 7, 2024 8:47 PM To: StarlingX ML <starlingx-discuss@lists.starlingx.io> Subject: Updating the overview slide deck CAUTION: This email comes from a non Wind River email account! Do not click links or open attachments unless you recognize the sender and know the content is safe. Hi StarlingX Community, I’m reaching out to you about the onboarding/overview slide deck[1] that we have on the Learn tab of the project’s website. The slide deck has a lot of diagrams, including ones that describe the Flock services, ones that go into the Kubernetes-related parts of the platform, as well as a couple of high level overview diagrams. It came up in the past that most of these diagrams need to be updated, since the platform has evolved quite a lot since they were originally drawn. I can update the diagrams in the slide deck, and work with the Foundation’s design team to get the ones updated that we use on the website and in the one-pager. Does anyone have any newer diagrams that you could share for guidance? Or, should we utilize some time on the community call to talk through which diagrams need updating and find volunteers who can sketch updated versions of them? Thanks and Best Regards, Ildikó [1] https://www.starlingx.io/collateral/StarlingX_Onboarding_Deck_for_Web.pdf ———
Ildikó Váncsa Director of Community Open Infrastructure Foundation <updated-DC-Diagram.pptx><updated-DC-Slides.pptx><updated-App-Mgmt-Slides - Copy.pptx>
participants (4)
-
Cervi, Thales Elero
-
Ildiko Vancsa
-
Waines, Greg
-
Webster, Steven