Skip to content
Open
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 removed assets/images/6_features.png
Binary file not shown.
2,530 changes: 2,530 additions & 0 deletions assets/images/6_features.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed assets/images/new_overview_integrators.png
Binary file not shown.
1 change: 1 addition & 0 deletions assets/images/new_overview_integrators.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed assets/images/open_cloud_arch-view.png
Binary file not shown.
1 change: 1 addition & 0 deletions assets/images/open_cloud_arch-view.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed assets/images/overview_architecture.png
Binary file not shown.
1 change: 1 addition & 0 deletions assets/images/overview_architecture.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed assets/images/overview_containers.png
Binary file not shown.
1 change: 1 addition & 0 deletions assets/images/overview_containers.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed assets/images/overview_edge-cluster.png
Binary file not shown.
1 change: 1 addition & 0 deletions assets/images/overview_edge-cluster.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed assets/images/overview_key-features.png
Binary file not shown.
1 change: 1 addition & 0 deletions assets/images/overview_key-features.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed assets/images/overview_resources.png
Binary file not shown.
1 change: 1 addition & 0 deletions assets/images/overview_resources.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed assets/images/overview_vdc.png
Binary file not shown.
1 change: 1 addition & 0 deletions assets/images/overview_vdc.svg
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 @@ -57,7 +57,7 @@ The first step in building a customized cluster is to decide on the hypervisor t

OpenNebula allows you to deploy heterogeneous multi-hypervisor environments managed by a single OpenNebula instance, so after installing the cloud with one hypervisor you can add another. The ability to gradually integrate open source hypervisors helps to protect existing IT investments and facilitates evaluation and testing, at the same time avoiding vendor lock-in by using open-source components.

![OpenNebula Hypervisors](/images/6_features.png)
{{< image path="/images/6_features.svg" alt="OpenNebula Hypervisors" align="center" width="50%" pb="20px" >}}

### 3.2. Install the Virtualization Hosts

Expand Down Expand Up @@ -118,4 +118,4 @@ Because no two clouds are the same, OpenNebula provides many different interface
- The **OneFlow API** to create, control, and monitor [multi-tier applications or services]({{% relref "../../../product/integration_references/system_interfaces/appflow_api#appflow-api" %}}) composed of interconnected Virtual Machines.
- A **Hook Manager** to [trigger administration scripts]({{% relref "../../../product/integration_references/system_interfaces/hook_driver#hooks" %}}) upon resource state changes or API calls.

![OpenNebula Cloud Architecture](/images/new_overview_integrators.png)
{{< image path="/images/new_overview_integrators.svg" alt="OpenNebula Cloud Architecture" align="center" width="50%" pb="20px" >}}
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ This document presents a powerful distributed Edge Cloud Architecture for OpenNe

We have defined this architecture to be much simpler than traditional cloud computing architectures, which are usually composed of complex, proprietary general-purpose software systems for storage and networking. This architecture has been created from the collective information and experiences of hundreds of users and client engagements for over ten years. It builds on storage and networking technologies that already exist in the Linux operating system and on modern storage hardware available from existing cloud and edge providers, leading to a greatly simplified design. Our Edge Cloud Architecture implements enterprise-grade cloud features for performance, availability, and scalability, with a very simple design that avoids vendor lock-in and reduces complexity, resource consumption, and operational costs.

![image](/images/overview_edge-cluster.png)
{{< image path="/images/overview_edge-cluster.svg" alt="Edge Cluster Architecture Overview" align="center" width="50%" pb="20px" >}}

{{< alert title="Note" color="success" >}}
The White Paper on the True Hybrid Cloud Architecture is publicly available for [download](https://support.opennebula.pro/hc/en-us/articles/360050302811-Edge-Cloud-Architecture-White-Paper).{{< /alert >}}
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ The OpenNebula Cloud Reference Architecture is a blueprint to guide IT architect

The document describes the reference architecture for Basic and Advanced OpenNebula Clouds, and provides recommended software for main architectural components and the rationale behind them. Each section also provides information about other open source infrastructure platforms tested and certified by OpenNebula to work in enterprise environments. As a complement to these certified components, the browseable OpenNebula add-on catalog offers further options supported by partners and by the OpenNebula community. This reference architecture does not include other components in the open cloud ecosystem that are important to consider at the time of designing a cloud, such as configuration management and automation tools for configuring cloud infrastructure and managing large numbers of devices.

![image](/images/open_cloud_arch-view.png)
{{< image path="/images/open_cloud_arch-view.svg" alt="OpenNebula Cloud Architecture Overview" align="center" width="50%" pb="20px" >}}

{{< alert title="Note" color="success" >}}
The White Paper on the Open Cloud Architecture is publicly available for [download](https://support.opennebula.pro/hc/en-us/articles/204210319-Open-Cloud-Reference-Architecture-White-Paper).{{< /alert >}}
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ weight: "4"

In a small installation with a few Hosts you can use OpenNebula without giving much thought to infrastructure partitioning and provisioning. However, for medium and large-scale deployments you will probably want to provide some level of isolation and structure. OpenNebula offers a flexible and powerful cloud provisioning model based on Virtual Data Centers (VDCs) that enables an integrated, comprehensive framework to dynamically provision the infrastructure resources in large multi-datacenter and multi-cloud environments to different customers, business units, or groups. Another key management task in an OpenNebula Infrastructure environment involves determining who can use the cloud interfaces and what tasks those users are authorized to perform. This White Paper is meant for cloud architects, builders, and administrators, to help them understand the OpenNebula models for managing and provisioning virtual resources, and default user roles in OpenNebula.

![image](/images/overview_vdc.png)
{{< image path="/images/overview_vdc.svg" alt="Cloud provisioning model based on Virtual Data Centers (VDCs)" align="center" width="50%" pb="20px" >}}

{{< alert title="Note" color="success" >}}
The White Paper of the Cloud Provisioning Models and User Roles is publicly available for [download](https://support.opennebula.pro/hc/en-us/articles/360018778938-Cloud-Provisioning-Models-and-User-Roles).{{< /alert >}}
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ This page provides a high-level overview of the OpenNebula cloud model, architec

OpenNebula is a **powerful, but easy-to-use, open source platform to build and manage enterprise clouds and virtualized Data Centers**. It combines existing virtualization technologies with advanced features for multi-tenancy, automatic provision and elasticity on private, hybrid, and edge environments. It unifies management of IT infrastructure and applications, preventing vendor lock-in and reducing complexity, resource consumption, and operational costs.

![><](/images/overview_key-features.png)
{{< image path="/images/overview_key-features.svg" alt="OpenNebula Key Features" align="center" width="50%" pb="20px" >}}

## OpenNebula Infrastructure and Management

Expand All @@ -35,7 +35,7 @@ OpenNebula can manage both single VMs and complex multi-tier services composed o

OpenNebula supports the automated deployment of Kubernetes clusters through a virtual appliance, **OneKE**, the OpenNebula Kubernetes Engine. OneKE is an enterprise-grade, CNCF-certified Kubernetes distribution based on SUSE Rancher RKE2. In its basic configuration it comprises four Virtual Machines: the Kubernetes master node, a VNF node, a storage node, and a worker node. It can be configured as a multi-master cluster for high availability, and easily scaled up to include more worker nodes, either before deployment or dynamically during operation, by using elasticity rules. It includes features such as MetalLB load balancing, Multus and Cilium CNI plugins, and Longhorn storage. It is available as a multi-VM appliance on the OpenNebula Marketplace and can be installed in minutes using Sunstone, OpenNebula’s web UI.

![><](/images/overview_containers.png)
{{< image path="/images/overview_containers.svg" alt="OneKE Architecture with Containerized Applications" align="center" width="50%" pb="20px" >}}

### Management Model and Tools

Expand All @@ -56,7 +56,7 @@ OpenNebula’s cloud provisioning model is based on Virtual Data Centers (VDCs)

A key management task in an OpenNebula infrastructure environment involves determining who can use the cloud administrative interfaces, and what tasks those users are authorized to perform. The person with the role of cloud service administrator is authorized to assign the appropriate rights required by other users. OpenNebula includes three default user roles: **cloud users**, **cloud operators**, and **cloud administrators**. OpenNebula further offers the possibility of designing custom roles. The OpenNebula documentation provides general guidelines and best practices for determining cloud user roles, please see [Cloud Access Models and Roles]({{% relref "cloud_access_model_and_roles#understand" %}}) for more information.

![><](/images/overview_vdc.png)
{{< image path="/images/overview_vdc.svg" alt="Cloud provisioning model based on Virtual Data Centers (VDCs)" align="center" width="50%" pb="20px" >}}

## The OpenNebula Model for Cloud Infrastructure Deployment

Expand All @@ -67,7 +67,7 @@ A standard OpenNebula Cloud Architecture consists of:

Infrastructure components may reside at different geographical locations. They are interconnected by multiple networks for internal storage and node management, and for private and public VM communications.

![><](/images/overview_resources.png)
{{< image path="/images/overview_resources.svg" alt="Standard OpenNebula Cloud Architecture" align="center" width="50%" pb="20px" >}}

In general, there are two types of cluster models that can be used with OpenNebula:

Expand All @@ -78,9 +78,7 @@ In general, there are two types of cluster models that can be used with OpenNebu

OpenNebula includes its own Edge Cluster configuration. Based on solid open source storage and networking technologies, OpenNebula’s Edge Cluster model is a much simpler approach than those of customized cloud architectures made of more complex, general purpose, and separate infrastructure components. An OpenNebula Edge Cluster can be deployed on-demand on virtual resources, on-premises, or on public cloud or edge providers to enable seamless hybrid cloud deployments.

![><](/images/overview_edge-cluster.png)

<!-- overview_edge-cluster.png -->
{{< image path="/images/overview_edge-cluster.svg" alt="Edge Cluster Architecture Overview" align="center" width="50%" pb="20px" >}}

### Customized Clusters

Expand All @@ -100,7 +98,7 @@ Organizations’ and users’ needs are varied, and constantly evolve over time.

OpenNebula was designed to be easily adapted to any infrastructure and easily extended with new components. The result is a modular system that can implement a variety of cloud architectures and interface with multiple data center services.

![><](/images/overview_architecture.png)
{{< image path="/images/overview_architecture.svg" alt="OpenNebula Components Following a Modular Approach" align="center" width="50%" pb="20px" >}}

<!-- overview-architecture.png -->

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ weight: "1"

OpenNebula has been designed to be easily adapted to any infrastructure and easily extended with new components. The result is a modular system that can implement a variety of cloud architectures and can interface with multiple datacenter services. In this Guide we review the main interfaces of OpenNebula and their.

![image0](/images/overview_architecture.png)
{{< image path="/images/overview_architecture.svg" alt="OpenNebula Components Following a Modular Approach" align="center" width="50%" pb="20px" >}}

## How Should I Read This Chapter

Expand Down