Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

F OpenNebula/One#5763: add fireedge federation conf. in slaves #3045

Merged
merged 1 commit into from
Sep 9, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file modified source/images/zoneswitchsunstone.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,6 @@ In this document, each configuration step starts with **Master** or **Slave** to

.. important:: The federation can be set up with MySQL/MariaDB or SQLite as backends, but you can't mix them across Zones. MySQL/MariaDB is recommended for production deployments.

.. important:: FireEdge, the next-generation server for the Sunstone GUI, currently does not support switching zones in a federation environment. Please connect directly to the zone that you wish to work on. Likewise, take into account that the FireEdge functionality enabled in Sunstone will not be available if you switch to a remote zone from within Sunstone.

Step 1. Configure the OpenNebula Federation Master Zone
================================================================================
Expand Down Expand Up @@ -113,6 +112,19 @@ Step 2. Adding a New Federation Slave Zone

- **Slave**: Start OpenNebula.

- **Slave**: In each Slave node you must place the configuration so that it is able to know which zone it represents. for this you must modify the ``/etc/one/fireedge-server.conf`` file with the zone information.

.. code-block:: bash

default_zone:
id: 100 //ID
name: 'Slave' // NAME
endpoint: 'http://<slave-ip>:2633/RPC2' //ENDPOINT

.. note:: In case the default :ref:`PORT <fireedge_conf>` of the FireEdge (Master or Slave) is changed, it is required that the zone that this fireedge represents has the ``FIREEDGE_ENDPOINT`` field added with the endpoint that the other FireEdge receives HTTPS requests.

- **Slave**: Start FireEdge.

The Zone should be now configured and ready to use.

Step 3. Adding HA to a Federation Slave Zone (Optional)
Expand Down
Loading