Hello,

Thank you for sharing these resources. I have gone through the documentation and found it quite insightful. I wanted to check if the scripts provided in these documents are suitable for a production setup. Are there any specific considerations or best practices to keep in mind when using them in a production environment?

Looking forward to your guidance.




---- On Tue, 04 Mar 2025 19:19:08 +0530 Doug Goldstein <doug@thegoldsteins.org> wrote ---

Hello,

You’ve already gotten some examples of OpenStack Helm but two others are:
- https://docs.rackspacecloud.com/
- https://rackerlabs.github.io/understack

OpenStack Helm is pretty flexible in what you make of it. Overall as operators I think we would probably do better to push some documentation changes upstream around usages and tweaks.

—
Doug



On Mar 3, 2025, at 3:44 PM, Karl Kloppenborg <kkloppenborg@resetdata.com.au> wrote:

Hello!
 
Yes I can confirm ResetData is utilising Openstack-Helm in a multi-az, multi-region compacity, we’ve had great success with it.
Obviously this comes with it’s own unique challenges and complexities, however if you have a good understanding of K8s, Helm and Openstack, it makes for a great operating environment.
 
Thanks,
Karl.
 


Karl Kloppenborg

Chief Technology Officer


m: +61 437 239 565
resetdata.com

<reset_69557fc2-1d63-4932-b5fd-93bd4f39ca7b.png>

ResetData supports Mandatory Client Related Financial Disclosures – Scope 3 Emissions Reporting
For more information on the phasing of these requirements for business please visit;  
https://treasury.gov.au/sites/default/files/2024-01/c2024-466491-policy-state.pdf

This email transmission is intended only for the addressee / person responsible for delivery of the message to such person and may contain confidential or privileged information. Confidentiality and legal privilege are not waived or lost by reason of mistaken delivery to you, nor may you use, review, disclose, disseminate or copy any information contained in or attached to it. Whilst this email has been checked for viruses, the sender does not warrant that any attachments are free from viruses or other defects. You assume all liability for any loss, damage or other consequences which may arise from opening or using the attachments. If you received this e-mail in error please delete it and any attachments and kindly notify us by immediately sending an email to contact@resetdata.com.au

From: Vladimir Kozhukalov <kozhukalov@gmail.com>
Date: Tuesday, 4 March 2025 at 5:36 am
To: Thamanna Farhath <thamanna.f@zybisys.com>
Cc: openstack-discuss <openstack-discuss@lists.openstack.org>
Subject: Re: [openstack-helm] Inquiry: OpenStack-Helm Deployment in Production Environments

Hi Thamanna,
 
Plenty of production deployments are managed by Openstack-Helm (often indirectly). Usually users have their downstream with some customizations and it is common practice to utilize additional orchestration tools. AT&T has been behind the project from its very beginning, also Vexxhost is using it with their Atmosphere, Mirantis also has their downstream based on Openstack-Helm with their custom operator (now open source), AFAIK ResetData (Australian cloud company) is also using Openstack-Helm with Terraform, Rackspace has been actively using (with ArgoCD if I remember correctly) and contributing to the project recently.
 
 
On Mon, Mar 3, 2025 at 2:30 AM Thamanna Farhath <thamanna.f@zybisys.com> wrote:

Hello OpenStack Community,

I hope this email finds you well.

I am currently exploring OpenStack-Helm for deploying OpenStack and would like to understand its adoption in live production environments. Specifically, I am interested in knowing if any cloud providers have successfully deployed and are operating OpenStack using OpenStack-Helm in production.

If there are any case studies, references, or experiences shared by operators who have implemented this deployment method, I would greatly appreciate any insights or guidance.

Looking forward to your valuable input.

 
 
 
 

Disclaimer :  The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.
 
E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."
 

 
--
Best regards,
Kozhukalov Vladimir




Disclaimer :  The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.

 

E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."