Skip to content

Commit

Permalink
M #-: New version for Quick Start (#2681)
Browse files Browse the repository at this point in the history 
- t2.medium for AWS VM
- Changes in Operations Guide

(cherry picked from commit 03f3cab)
(cherry picked from commit 13dc6a3)
(cherry picked from commit d831421)
  • Loading branch information
@imllorente @rsmontero
imllorente authored and rsmontero committed Sep 14, 2023
1 parent 41f4359 commit d76a161
Show file tree
Hide file tree
Showing 2 changed files with 34 additions and 23 deletions.
54 changes: 33 additions & 21 deletions source/quick_start/deployment_basics/try_opennebula_on_kvm.rst
View file
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,11 @@
Deploy OpenNebula Front-end on AWS
==================================

In this guide, we'll go through a Front-end OpenNebula environment deployment, where all the OpenNebula services needed to use, manage and run the cloud will be collocated on a single dedicated bare-metal Host. Afterwards, you can continue to the Operations Basics section to add a remote Edge Cluster based on KVM to your shiny new OpenNebula cloud!
In this guide, we'll go through a Front-end OpenNebula environment deployment, where all the OpenNebula services needed to use, manage and run the cloud will be collocated on a single dedicated bare-metal server or virtual machine. You will be also able to deploy a local KVM node within the same single server or virtual machine to try out OpenNebula, or for daily development work. Afterwards, if you need more resources or want to try out the automatic provisioning features for building multi-provider hybrid clouds, you can continue to the :ref:`Operations Guide <operation_basics>` to add a remote Edge Cluster based on KVM using AWS bare-metal instances to your shiny new OpenNebula cloud!

While all the :ref:`installation and configuration <opennebula_installation>` steps can be done manually and would give you a better insight and control over what and how it is configured, we'll focus on the most straightforward approach by leveraging the miniONE tool.

The miniONE tool is a simple deployment script that deploys an OpenNebula Front-end. This tool is mainly intended for evaluation, development, and testing, but can also be used as a base for larger short-lived deployments. Usually, it takes just a few minutes to get the environment ready.
The miniONE tool is a simple deployment script that deploys an OpenNebula Front-end and, optionaly, a single KVM node within a single physical or virtual machine. This tool is mainly intended for evaluation, development, and testing, but can also be used as a base for larger short-lived deployments. Usually, it takes just a few minutes to get the environment ready.

Requirements
============
Expand All @@ -27,9 +27,9 @@ If you don't have a server available with the above characteristics, we recommen

- Frankfurt region
- Ubuntu Server 20.04 LTS (HVM), SSD Volume Type - ami-0767046d1677be5a0
- t2.small
- 100 GB hard disk (you need to edit the Storage tab before launching the instance; by default it comes with just 8GB. It can be lower -40GB- if you are not planning to test the K8s appliance)
- before launching the instance, please open the ports defined above by editing the Security Groups as per the picture. This can also happen after launching the instance following `this guide <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html>`__.
- t2.medium
- 40 GB hard disk (you need to edit the Storage tab before launching the instance; by default it comes with just 8GB
- open ports 22 (SSH), 80 (Sunstone), 2616 (FireEdge), 5030 (OneGate) by editing the Security Groups as per the picture. This can also happen after launching the instance following `this guide <https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/authorizing-access-to-an-instance.html>`__.

|aws_security_groups|

Expand Down Expand Up @@ -64,21 +64,23 @@ Various command line parameters passed to the miniONE tool can customize the dep

In most cases, it's not necessary to specify anything, simply proceed with installation.

Deployment of Front-End
=======================
Deployment of Front-End and KVM Node
====================================

Run the following command under the privileged user **root** to get ready the all-in-one OpenNebula Front-end installation:
Run the following command under the privileged user **root** to deploy an evaluation cloud with an all-in-one front-end and a single KVM node:

.. prompt:: bash # auto

# sudo bash minione --frontend
# sudo bash minione

This option is suitable for bare-metal hosts to utilize HW virtualization. The deployment will fallback to emulation (QEMU) if running on virtual machine or CPU without virtualization capabilities.

Be patient, it should take only a few minutes to get the Host prepared. The main deployment steps are logged on the terminal, and at the end of a successful deployment the miniONE tool provides a report with connection parameters and initial credentials. For example:

.. code::
### Report
OpenNebula 6.4 was installed
OpenNebula 6.6 was installed
Sunstone is running on:
http://3.121.76.103/
FireEdge is running on:
Expand All @@ -87,20 +89,20 @@ Be patient, it should take only a few minutes to get the Host prepared. The main
user: oneadmin
password: lCmPUb5Gwk
The OpenNebula Front-end is now ready for evaluation.
.. note:: When running miniONE within an AWS instance, the reported IP may be a private address that's not reachable over the Internet. Use its public IP address to connect to the FireEdge and Sunstone services.

.. note:: miniONE offers more functionality. You can install OpenNebula with a KVM Host (next section) if you have a processor with virtualization capabilities. Just drop the --Front-end flag to enable this if interested.
The OpenNebula Front-end and local KVM node are now ready for evaluation.

Deployment of Front-End and KVM Node
====================================
.. note:: miniONE offers more functionality. For example, you can install an OpenNebula front-end without a KVM Host (next section). Just add the --Front-end flag to enable this if interested.

Run the following commands to deploy an evaluation cloud with a front-end and a single KVM node:
Deployment of Front-End
=======================

.. prompt:: bash # auto
If you do not want to create a local KVM node, run the following command to get ready the OpenNebula Front-end installation:

# sudo bash minione
.. prompt:: bash # auto

This option is suitable for bare-metal hosts to utilize HW virtualization. The deployment will fallback to emulation (QEMU) if running on virtual machine or CPU without virtualization capabilities.
# sudo bash minione --frontend

Validation
==========
Expand All @@ -113,9 +115,19 @@ If the Host configured by **miniONE** is behind the firewall, the (default) Suns

.. |images-sunstone-dashboard| image:: /images/sunstone-dashboard.png

With the default Admin View you can do anything in OpenNebula. Switch to the Cloud View (oneadmin-->Views-->cloud) to see how a final user will see OpenNebula.

The Cloud View interface is much simpler and targeted at end users.

If you created a local KVM node with the front-end you can continue the validation with the following steps:

- Create a new Virtual Machine by clicking the ‘+’ button. Select the only available template and click ‘Create’.
- After clicking ‘Create’ you will be taken to the dashboard where you can see your running VMs.
- You can click on your VM and manage it: Save its state, Reboot it, etc:

.. note:: We know, thesea are very basic steps. If you want to try out real-life workloads with public IPs please continue to next section.

Next Steps
==========

After reaching this point, if you created a KVM node, you can follow the Running Virtual Machines section in the :ref:`Usage Basica Guide <usage_basics>`.

If you want to try out instead OpenNebula public resource infrastructure provisioning or the Kubernestes engine, we recommend following the :ref:`Operations Guide <operation_basics>` from Quick Start after finishing this guide to add computing power to your shiny new OpenNebula cloud.
if you want to continue the evaluation with physical resources for VMs and Kubernetes clusters or try out the automatic provisioning features for building multi-provider hybrid clouds, you can follow the :ref:`Operations Guide <operation_basics>` to add a remote Edge Cluster based on KVM using AWS bare-metal instances to your shiny new OpenNebula cloud!
3 changes: 1 addition & 2 deletions source/quick_start/operation_basics/provisioning_edge_cluster.rst
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,7 @@ In this section you can check all the steps needed to deploy an **Edge 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:: If you're using OpenNebula 6.6.0 CE, before adding hosts to your environment, please apply this `patch <https://gist.github.com/tinova/73aa9ae5a7b35000563fa5801c7465c5>`__ in all Frontend machines:
.. 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:

.. code-block:: diff
Expand Down

0 comments on commit d76a161

Please sign in to comment.