> is that also mean the network traffic will not go through the
multiple ha-proxy of OKD ?

I am not aware of all the details of OKD, but I assume ha-proxy is used as an ingress balancer. So the management traffic (when you access to Openstack API from outside) will be balanced between Openstack API pods. However the VM traffic is managed by Openstack networking components (Neutron, Octavia, ...).

On Fri, Mar 7, 2025 at 3:03 AM Francesco Di Nucci <francesco.dinucci@na.infn.it> wrote:

Hi

My two cents - "ease" of upgrade is more related to planning the
OpenStack components setup than to the deployment method

An alternative for bare metal is use a couple of servers as KVM
hypervisors to host management VMs (Keystone, Cinder etc) and install
Nova compute on the other ones, automating with Foreman+Puppet

--
Francesco Di Nucci
System Administrator
Compute & Networking Service, INFN Naples

Email: francesco.dinucci@na.infn.it

On 05/03/25 17:19, Albert Shih wrote:
> Hi everyone
>
> Long time ago I deploy a openstack mostly manually, then I integrated in
> our deployment tool (puppet).
>
> Now I need to re-install everything. I'm searching the «best» method to do
> that.
>
> My deployment would be on bare-metal, I don't need/want a deployment of
> CEPH (I already have my ceph cluster). Just need the cinder to use the
> ceph.
>
> The main focus is the easy way to upgrade. I don't have a lot of hardware
> so I can afford to have a «test» cluster for upgrading.
>
> I'm thinking of kolla, what do you think ?
>
> I see they are now openstack-helm project, which If I understand correctly
> use a k8s to manage the deployment of openstack. Is that correct ?
>
> With those tools is they are any limitation about the result ? Or can I got
> the most the main features of openstack ?
>
> What would you recommend ?
>
> Regards.