<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>OpenStack IaaS on Documentation</title>
    <link>/docs/openstack-iaas/</link>
    <description>Recent content in OpenStack IaaS on Documentation</description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="/docs/openstack-iaas/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Announcements</title>
      <link>/docs/openstack-iaas/announcement/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/openstack-iaas/announcement/</guid>
      <description>&lt;h2 id=&#34;2026-03-31-elastx-cloud-platform---compute-storage-and-dbaas&#34;&gt;2026-03-31 Elastx Cloud Platform - Compute, Storage and DBaaS&lt;/h2&gt;&#xA;&lt;h3 id=&#34;pricing-adjustment&#34;&gt;Pricing adjustment&lt;/h3&gt;&#xA;&lt;p&gt;We have absorbed rising operational costs rather than pass them on to you. Despite significant inflationary pressure across the industry, we have managed to keep our prices stable.&lt;/p&gt;&#xA;&lt;p&gt;The primary driver for our price adjustment is a sharp increase in hardware costs, which have risen 150–250% in the last 6 months. This is a market-wide development entirely outside our control, and one we have worked hard to shield you from for as long as possible. We have reached a point where continuing to do so would compromise our ability to maintain and develop the platform in a sustainable way.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Overview</title>
      <link>/docs/openstack-iaas/overview/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/openstack-iaas/overview/</guid>
      <description>&lt;p&gt;&lt;em&gt;ELASTX OpenStack IaaS&lt;/em&gt; consists of a fully redundant installation spread over three different physical locations (openstack availability zones) in Stockholm, Sweden. Managed and monitored by us 24x7. You also have access to our support at any time.&lt;/p&gt;&#xA;&lt;p&gt;The current setup is based on &lt;a href=&#34;https://docs.openstack.org/yoga/user/&#34;&gt;the OpenStack version Yoga&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;/img/dc-1.png&#34; alt=&#34;Overview of OpenStack IaaS data centers&#34;&gt;&lt;/p&gt;&#xA;&lt;h2 id=&#34;services&#34;&gt;Services&lt;/h2&gt;&#xA;&lt;p&gt;Our OpenStack environment currently runs the following services:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Keystone - Authentication service&lt;/li&gt;&#xA;&lt;li&gt;Nova - Compute service&lt;/li&gt;&#xA;&lt;li&gt;Neutron - Network service&lt;/li&gt;&#xA;&lt;li&gt;Heat - Orchestration service&lt;/li&gt;&#xA;&lt;li&gt;Horizon - Dashboard&lt;/li&gt;&#xA;&lt;li&gt;Glance - Image store. We provide images for the most popular operating systems. All Linux images are unmodified from the official vendor cloud image.&lt;/li&gt;&#xA;&lt;li&gt;Barbican - Secret store service which is powered by physical HSM appliances&lt;/li&gt;&#xA;&lt;li&gt;Octavia - Load balancer service, barbican integration for SSL termination&lt;/li&gt;&#xA;&lt;li&gt;Cinder - Block storage with SSD based block storage and guaranteed IOPS reservations which is integrated with Barbican for optional encrypted volumes.&lt;/li&gt;&#xA;&lt;li&gt;Swift - Object storage&lt;/li&gt;&#xA;&lt;li&gt;Ceilometer - Metric storage, stores key metrics for the services like cpu and memory utilization&lt;/li&gt;&#xA;&lt;li&gt;CloudKitty - Rating service&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;quotas&#34;&gt;Quotas&lt;/h2&gt;&#xA;&lt;p&gt;These are our default project quotas, let us know if you wish to change these&#xA;upon ordering. Contact support to have quotas changed on an existing project.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Network</title>
      <link>/docs/openstack-iaas/network/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>/docs/openstack-iaas/network/</guid>
      <description>&lt;h2 id=&#34;overview&#34;&gt;Overview&lt;/h2&gt;&#xA;&lt;p&gt;The OpenStack tenant networks is implemented as a shared L2 between all availability zones and is tightly integrated with our network infrastructure.&#xA;Routing is handled by anycast routing in the switch infrastruture which makes the network extremely performant with low consistent latency.&lt;/p&gt;&#xA;&lt;h2 id=&#34;special-considerations&#34;&gt;Special considerations&lt;/h2&gt;&#xA;&lt;h3 id=&#34;router-egress-nat&#34;&gt;Router Egress NAT&lt;/h3&gt;&#xA;&lt;p&gt;Egress NAT is distributed and handled by the local hypervisor which means that unless a floating ip is associated with a instance it will utilize the public ip-address of the hypervisor where the instance is currently running. If the public ip-address of the instance needs to be known, e.g. needs to be provided to a 3rd party for firewall rules or likewise a floating ip needs to be associated with the instance.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
