Karl Kloppenborg |
m: +61 437 239 565 |
ResetData supports Mandatory Client
Related Financial Disclosures – Scope 3 Emissions Reporting |
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 |
You don't often get email from thamanna.f@zybisys.com.
Learn why this is important
|
Hello OpenStack Community,
I hope you are doing well.
I am currently deploying OpenStack on top of a Kubernetes cluster using OpenStack Helm and aiming to install the 2023.1 (Antelope) version. However, I am facing difficulties in installing this specific version via Helm charts. Despite my
attempts, I have not been able to successfully deploy the required OpenStack services for this release.
Additionally, I am ensuring that the dependent services, such as RabbitMQ, align with the compatibility requirements of OpenStack 2023.1. As per the OpenStack documentation, RabbitMQ 3.11 is the recommended version, but I encountered
issues while deploying it. Instead, I found that RabbitMQ 3.12 works without any issues.
I would like to know:
I would appreciate any guidance, best practices, or documentation references that could help resolve these challenges.
Looking forward to your valuable insights.
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."