<?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>https://docs.opennebula.io/7.2/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="https://docs.opennebula.io/7.2/product/control_plane_configuration/data_center_federation/index.xml" rel="self" type="application/rss+xml"/><item><title>Overview</title><link>https://docs.opennebula.io/7.2/product/control_plane_configuration/data_center_federation/overview/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/control_plane_configuration/data_center_federation/overview/</guid><description>&lt;p&gt;&lt;a id="introf"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Overview --&gt;
&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>https://docs.opennebula.io/7.2/product/control_plane_configuration/data_center_federation/config/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/control_plane_configuration/data_center_federation/config/</guid><description>&lt;p&gt;&lt;a id="federationconfig"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Federation Configuration --&gt;
&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;
&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;
&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>https://docs.opennebula.io/7.2/product/control_plane_configuration/data_center_federation/usage/</link><pubDate>Mon, 17 Feb 2025 00:00:00 +0000</pubDate><guid>https://docs.opennebula.io/7.2/product/control_plane_configuration/data_center_federation/usage/</guid><description>&lt;p&gt;&lt;a id="federationmng"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;!--# Federation Usage --&gt;
&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;
&lt;h2 id="sunstone"&gt;Sunstone&lt;/h2&gt;
&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>