Skip to content

Commit

Permalink
Update provisioning_edge_cluster.rst
Browse files Browse the repository at this point in the history
  • Loading branch information
imllorente authored Sep 14, 2023
1 parent 64e2075 commit d2c71b8
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,9 @@ Provisioning an Edge Cluster

In this section you can check all the steps needed to deploy an **Edge Cluster**. This involves the FireEdge OneProvision GUI and Sunstone to manage the resources created in OpenNebula. Each new provision in the OneProvision GUI creates a new OpenNebula cluster.

.. important:: This guide assumes that you have deployed the OpenNebula front-end following the :ref:`Deployment Basics guide <deployment_basics>`. Here we'll be creating a metal Edge Cluster with KVM hypervisor, suitable for deploying both Virtual Machines and K8s clusters in the following :ref:`Usage Basics section <usage_basics>`.
.. important:: This guide assumes that you have deployed the OpenNebula front-end or you have access to a hosted frontend following the :ref:`Deployment Basics guide <deployment_basics>`. Here we'll be creating a metal Edge Cluster with KVM hypervisor, suitable for deploying both Virtual Machines and K8s clusters in the following :ref:`Usage Basics section <usage_basics>`.

.. important:: If you're using OpenNebula 6.6.0 CE, before adding hosts to your environment, please create a oneprovision-repo.patch file with this `patch <https://gist.github.com/tinova/73aa9ae5a7b35000563fa5801c7465c5>`__ in your Frontend machine and then execute the below commands:
.. important:: If you're using your own deployment with OpenNebula 6.6.0 CE, before adding hosts to your environment, please create a oneprovision-repo.patch file with this `patch <https://gist.github.com/tinova/73aa9ae5a7b35000563fa5801c7465c5>`__ in your Frontend machine and then execute the below commands:

.. prompt:: bash # auto

Expand Down

0 comments on commit d2c71b8

Please sign in to comment.