<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Data Center Federation on </title>
    <link>http://51.159.138.137:8082/devel/product/control_plane_configuration/data_center_federation/</link>
    <description>Recent content in Data Center Federation on </description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 17 Feb 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://51.159.138.137:8082/devel/product/control_plane_configuration/data_center_federation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Overview</title>
      <link>http://51.159.138.137:8082/devel/product/control_plane_configuration/data_center_federation/overview/</link>
      <pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate>
      <guid>http://51.159.138.137:8082/devel/product/control_plane_configuration/data_center_federation/overview/</guid>
      <description>&lt;p&gt;&lt;a id=&#34;introf&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;!--# Overview --&gt;&#xA;&lt;p&gt;The OpenNebula &lt;strong&gt;Federation&lt;/strong&gt; is a tightly coupled integration of several instances of OpenNebula Front-end (called &lt;strong&gt;Zones&lt;/strong&gt;), where each instance (Zone) shares the same user accounts, groups, and permissions configuration. You can define access policies federation-wide where users can be restricted to certain Zones, or to specific Clusters inside a Zone. Federation topology consists of one master and several slave Front-ends (any other federation configurations, e.g. deeper master-slave hierarchy, aren’t supported).&lt;/p&gt;</description>
    </item>
    <item>
      <title>Federation Configuration</title>
      <link>http://51.159.138.137:8082/devel/product/control_plane_configuration/data_center_federation/config/</link>
      <pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate>
      <guid>http://51.159.138.137:8082/devel/product/control_plane_configuration/data_center_federation/config/</guid>
      <description>&lt;p&gt;&lt;a id=&#34;federationconfig&#34;&gt;&lt;/a&gt;&lt;/p&gt;&#xA;&lt;!--# Federation Configuration --&gt;&#xA;&lt;p&gt;This section will explain how to configure two (or more) OpenNebula Zones to work as federation &lt;em&gt;master&lt;/em&gt; and &lt;em&gt;slave&lt;/em&gt;. The process described here can be applied to new installations or existing OpenNebula instances.&lt;/p&gt;&#xA;&lt;p&gt;OpenNebula &lt;em&gt;master&lt;/em&gt; Zone server replicates database changes on &lt;em&gt;slaves&lt;/em&gt; using a federated log. The log contains the SQL commands which should be applied in all Zones.&lt;/p&gt;&#xA;&lt;p&gt;In this document, each configuration step starts with &lt;strong&gt;Master&lt;/strong&gt; or &lt;strong&gt;Slave&lt;/strong&gt; to indicate the server where the step must be performed.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Federation Usage</title>
      <link>http://51.159.138.137:8082/devel/product/control_plane_configuration/data_center_federation/usage/</link>
      <pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate>
      <guid>http://51.159.138.137:8082/devel/product/control_plane_configuration/data_center_federation/usage/</guid>
      <description>&lt;p&gt;A user will have access to all the Zones where at least one of his or her groups has VDC resources. This access be can done through Sunstone or the CLI.&lt;/p&gt;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&#xA;&lt;ul class=&#34;nav nav-tabs&#34; id=&#34;tabs-0&#34; role=&#34;tablist&#34;&gt;&#xA;  &lt;li class=&#34;nav-item&#34;&gt;&#xA;      &lt;button class=&#34;nav-link disabled&#34;&#xA;          id=&#34;tabs-00-00-tab&#34; data-bs-toggle=&#34;tab&#34; data-bs-target=&#34;#tabs-00-00&#34; role=&#34;tab&#34;&#xA;          aria-controls=&#34;tabs-00-00&#34; aria-selected=&#34;false&#34;&gt;&#xA;        &lt;strong&gt;Interfaces&lt;/strong&gt;:&#xA;      &lt;/button&gt;&#xA;    &lt;/li&gt;&lt;li class=&#34;nav-item&#34;&gt;&#xA;      &lt;button class=&#34;nav-link active&#34;&#xA;          id=&#34;tabs-00-01-tab&#34; data-bs-toggle=&#34;tab&#34; data-bs-target=&#34;#tabs-00-01&#34; role=&#34;tab&#34;&#xA;          data-td-tp-persist=&#34;sunstone&#34; aria-controls=&#34;tabs-00-01&#34; aria-selected=&#34;true&#34;&gt;&#xA;        Sunstone&#xA;      &lt;/button&gt;&#xA;    &lt;/li&gt;&lt;li class=&#34;nav-item&#34;&gt;&#xA;      &lt;button class=&#34;nav-link&#34;&#xA;          id=&#34;tabs-00-02-tab&#34; data-bs-toggle=&#34;tab&#34; data-bs-target=&#34;#tabs-00-02&#34; role=&#34;tab&#34;&#xA;          data-td-tp-persist=&#34;cli&#34; aria-controls=&#34;tabs-00-02&#34; aria-selected=&#34;false&#34;&gt;&#xA;        CLI&#xA;      &lt;/button&gt;&#xA;    &lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&#xA;&lt;div class=&#34;tab-content&#34; id=&#34;tabs-0-content&#34;&gt;&#xA;    &lt;div class=&#34;tab-body tab-pane fade&#34;&#xA;        id=&#34;tabs-00-00&#34; role=&#34;tabpanel&#34; aria-labelled-by=&#34;tabs-00-00-tab&#34; tabindex=&#34;0&#34;&gt;&#xA;        &#xA;    &lt;/div&gt;&#xA;    &lt;div class=&#34;tab-body tab-pane fade show active&#34;&#xA;        id=&#34;tabs-00-01&#34; role=&#34;tabpanel&#34; aria-labelled-by=&#34;tabs-00-01-tab&#34; tabindex=&#34;0&#34;&gt;&#xA;        &lt;p&gt;In the upper right corner of the Sunstone page, users will see a globe icon next to the name of the Zone currently being used. If the user clicks on that, he or she will get a dropdown with all the accessible Zones. Clicking on any of the Zones in the dropdown will get the user to that Zone.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
