<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Kolla-Ansible on Manuel Chichi</title>
    <link>http://manuelchichi.com.ar/tags/kolla-ansible/</link>
    <description>Recent content in Kolla-Ansible on Manuel Chichi</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>2026 | Server icons created by RaftelDesign - Flaticon |</copyright>
    <lastBuildDate>Sat, 14 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://manuelchichi.com.ar/tags/kolla-ansible/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Upgrading OpenStack to the latest release</title>
      <link>http://manuelchichi.com.ar/projects/private-cloud/entry-2026-11-14/</link>
      <pubDate>Sat, 14 Nov 2026 00:00:00 +0000</pubDate>
      <guid>http://manuelchichi.com.ar/projects/private-cloud/entry-2026-11-14/</guid>
      <description>&lt;p&gt;This is a continuation of
&lt;a href=&#34;http://manuelchichi.com.ar/projects/private-cloud/entry-2026-11-07/&#34;&gt;moving the private cloud to a mini PC&lt;/a&gt;.
The cloud was still running OpenStack 2025.1, an older release. This post covers
how I brought it up to the latest release, 2026.2.&lt;/p&gt;
&lt;h1 id=&#34;why-keeping-software-updated-matters&#34;&gt;Why keeping software updated matters&lt;/h1&gt;
&lt;p&gt;Updating isn&amp;rsquo;t only about new features. Each release stops getting security fixes
after a while, so an old version keeps known vulnerabilities open. A private
cloud is still a network service, so it needs the same care as any other server.
Kolla-Ansible is also tied to specific OpenStack releases, so staying on a
supported version keeps the deployment tools working. Small, regular updates are
also easier than one large upgrade later.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
