admin/3engines_doc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

brand changed

Browse Source
This commit is contained in:
govardhan
2025-07-04 09:34:25 +05:30
parent 1ee37aea8b
commit faadd4e38d
129 changed files with 1069 additions and 1068 deletions
Download Patch File Download Diff File Expand all files Collapse all files

42
docs/cloud/OpenStack-user-roles-on-3Engines-Cloud.html.md → docs/cloud/3Engines-user-roles-on-3Engines-Cloud.html.md
View File

@ -1,9 +1,9 @@
OpenStack User Roles on 3Engines Cloud[🔗](#openstack-user-roles-on-brand-name "Permalink to this headline")
3Engines User Roles on 3Engines Cloud[🔗](#3Engines-user-roles-on-brand-name "Permalink to this headline")
=============================================================================================================
A **user role** in OpenStack cloud is a set of permissions that govern how members of specific groups interact with system resources, their access scope, and capabilities.
A **user role** in 3Engines cloud is a set of permissions that govern how members of specific groups interact with system resources, their access scope, and capabilities.
This guide simplifies OpenStack roles for casual users of 3Engines Cloud VMs. It focuses on practical use cases and commonly required roles.
This guide simplifies 3Engines roles for casual users of 3Engines Cloud VMs. It focuses on practical use cases and commonly required roles.
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
@ -32,24 +32,24 @@ You need a 3Engines Cloud hosting account with Horizon access: <https://horizon.
Also see:
[What is an OpenStack project on 3Engines Cloud](What-is-an-OpenStack-project-on-3Engines-Cloud.html.md)
[What is an 3Engines project on 3Engines Cloud](What-is-an-3Engines-project-on-3Engines-Cloud.html.md)
[What is an OpenStack domain on 3Engines Cloud](What-is-an-OpenStack-domain-on-3Engines-Cloud.html.md)
[What is an 3Engines domain on 3Engines Cloud](What-is-an-3Engines-domain-on-3Engines-Cloud.html.md)
[How to generate or use Application Credentials via CLI on 3Engines Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md)
**2. Familiarity with OpenStack Commands**
**2. Familiarity with 3Engines Commands**
Ensure you know the following OpenStack commands:
Ensure you know the following 3Engines commands:
**openstack**
: The primary CLI for interacting with OpenStack services.
[How to install OpenStackClient for Linux on 3Engines Cloud](../openstackcli/How-to-install-OpenStackClient-for-Linux-on-3Engines-Cloud.html.md)
**3Engines**
: The primary CLI for interacting with 3Engines services.
[How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md)
**kubectl**
: CLI for Kubernetes clusters. Example article:
[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud OpenStack Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-OpenStack-Magnum.html.md)
[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md)
Frequently used user roles[🔗](#frequently-used-user-roles "Permalink to this headline")
---------------------------------------------------------------------------------------
@ -61,22 +61,22 @@ Frequently used user roles[🔗](#frequently-used-user-roles "Permalink to this
Note
Older OpenStack versions may use **\_member\_**. If both **member** and **\_member\_** exist, choose **member**.
Older 3Engines versions may use **\_member\_**. If both **member** and **\_member\_** exist, choose **member**.
* Horizon: **Project** -> **Overview**
* CLI: **openstack server list**, **openstack project list**
* CLI: **3Engines server list**, **3Engines project list**
**observer**
: Read-only access for monitoring and auditing resources. Suitable for third-party tools like Prometheus or Grafana.
* Horizon: **Project** -> **Overview**
* CLI: **openstack server show**, **openstack project show**
* CLI: **3Engines server show**, **3Engines project show**
**reader**
: Read-only access with slightly broader permissions than **observer**. Ideal for monitoring and analytics tools requiring detailed resource data.
* Horizon: **Project** -> **Overview**
* CLI: **openstack server list**, **openstack project list**
* CLI: **3Engines server list**, **3Engines project list**
### Roles for Kubernetes users[🔗](#roles-for-kubernetes-users "Permalink to this headline")
@ -104,13 +104,13 @@ Frequently used user roles[🔗](#frequently-used-user-roles "Permalink to this
: Grants access to deploy applications behind load balancers.
* Horizon: **Network** -> **Load Balancers**
* CLI: **openstack loadbalancer member create**, **openstack loadbalancer member list**
* CLI: **3Engines loadbalancer member create**, **3Engines loadbalancer member list**
**load-balancer\_observer**
: Read-only access to monitor load balancer configurations.
* Horizon: **Network** -> **Load Balancers**
* CLI: **openstack loadbalancer show**, **openstack loadbalancer stats show**
* CLI: **3Engines loadbalancer show**, **3Engines loadbalancer stats show**
How to View Roles in Horizon[🔗](#how-to-view-roles-in-horizon "Permalink to this headline")
-------------------------------------------------------------------------------------------
@ -123,7 +123,7 @@ You can view roles in Horizon by navigating to **Identity** -> **Roles**.
Assigning multiple roles is best done during project creation rather than user creation.
![openstack-user-roles-create-4.png](../_images/openstack-user-roles-create-4.png)
![3Engines-user-roles-create-4.png](../_images/3Engines-user-roles-create-4.png)
Examples of using user roles[🔗](#examples-of-using-user-roles "Permalink to this headline")
-------------------------------------------------------------------------------------------
@ -132,7 +132,7 @@ The following articles, as one of many steps, describe how to assign a role to t
### Using user roles while creating application credential in Horizon[🔗](#using-user-roles-while-creating-application-credential-in-horizon "Permalink to this headline")
Normally, you access the cloud via user credentials, which may be one- or two-factor credentials. OpenStack provides a more direct procedure of gaining access to cloud with application credential and you can create a credential with several user roles.
Normally, you access the cloud via user credentials, which may be one- or two-factor credentials. 3Engines provides a more direct procedure of gaining access to cloud with application credential and you can create a credential with several user roles.
That S3 article selects user roles when creating an application credential, through Horizon:
@ -152,7 +152,7 @@ Here is how to specify user roles through CLI parameters:
### Using user roles while creating a new project[🔗](#using-user-roles-while-creating-a-new-project "Permalink to this headline")
In article [How to Create and Configure New Openstack Project Through Horizon on 3Engines Cloud Cloud](../openstackcli/How-To-Create-and-Configure-New-Project-on-3Engines-Cloud-Cloud.html.md) we use command **Project Members** to define which users to include into the project:
In article [How to Create and Configure New 3Engines Project Through Horizon on 3Engines Cloud Cloud](../3Enginescli/How-To-Create-and-Configure-New-Project-on-3Engines-Cloud-Cloud.html.md) we use command **Project Members** to define which users to include into the project:
![user-roles-list-create-4.png](../_images/user-roles-list-create-4.png)
@ -169,7 +169,7 @@ You would then continue by defining the roles for each user in the project:
### Using member role only while creating a new user[🔗](#using-member-role-only-while-creating-a-new-user "Permalink to this headline")
In SLURM article, we first create a new OpenStack Keystone user, with the role of **member**.
In SLURM article, we first create a new 3Engines Keystone user, with the role of **member**.
/cuttingedge/Sample-SLURM-Cluster-on-3Engines-Cloud-Cloud-with-ElastiCluster

24
docs/cloud/DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md
View File

@ -16,9 +16,9 @@ DNS as a Service (DNSaaS) provides functionality of managing configuration of us
| SSHFP | SSH Public Key Fingerprint |
| TXT | Text record |
DNS configuration management is available via OpenStack web dashboard (Horizon), OpenStack command line interface as well as via the API.
DNS configuration management is available via 3Engines web dashboard (Horizon), 3Engines command line interface as well as via the API.
DNS records management is performed on the level of an OpenStack project.
DNS records management is performed on the level of an 3Engines project.
Since DNSaaS purpose is to deal with external domain names, the internal name resolution (name resolution for private IP addresses within user’s projects) is not covered by this documentation.
@ -31,7 +31,7 @@ What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this
> * Adding new record for the domain
> * Adding records for subdomains
> * Managing records
> * Limitations in OpenStack DNSaaS
> * Limitations in 3Engines DNSaaS
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
@ -40,7 +40,7 @@ No. 1 **Account**
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://horizon.3Engines.com>.
No. 2 **Must have access to a project in 3Engines Cloud OpenStack account**
No. 2 **Must have access to a project in 3Engines Cloud 3Engines account**
If you are a tenant manager, you will be able to either use the existing basic project or create new projects for yourself or your users.
@ -53,7 +53,7 @@ We assume you already have a
> * basic knowledge of Domain Name Service principles as well as
> * understanding of the purpose of DNS records.
If not, please see [DNS article on Wikipedia](https://en.wikipedia.org/wiki/Domain_Name_System) or [OpenStack DNSaaS command line reference](https://docs.openstack.org/python-designateclient/latest/user/shell-v2.html.md)
If not, please see [DNS article on Wikipedia](https://en.wikipedia.org/wiki/Domain_Name_System) or [3Engines DNSaaS command line reference](https://docs.3Engines.org/python-designateclient/latest/user/shell-v2.html.md)
No. 4 **Must have domain purchased from a registrar**
@ -107,7 +107,7 @@ Step 2 Zone configuration[🔗](#step-2-zone-configuration "Permalink to this he
Zone configuration is defining parameters for the main domain name you have purchased.
To manage domain *exampledomain.com* in OpenStack, login to OpenStack dashboard, choose the right project if different than default, go to **Project** → **DNS** → **Zones**, click **Create Zone** and fill in the required fields:
To manage domain *exampledomain.com* in 3Engines, login to 3Engines dashboard, choose the right project if different than default, go to **Project** → **DNS** → **Zones**, click **Create Zone** and fill in the required fields:
![dns1.png](../_images/dns1.png)
@ -117,9 +117,9 @@ Here is what the parameters mean:
> * **Description**: free text description
> * **Email Address**: an administrative e-mail address associated with the domain
> * **TTL**: *Time To Live* in seconds - a period of time between refreshing cache in DNS servers. Please note that the longer time, the faster will be name recognition for your domain by external DNS servers but also if you introduce changes, they will propagate slower. The default value of 3600 seconds is a reasonable compromise.
> * **Type**: You may choose if OpenStack name servers will be primary or secondary for your domain. Default: Primary. In case you want to setup secondary name servers, you just define IP addresses or master DNS servers for the domain.
> * **Type**: You may choose if 3Engines name servers will be primary or secondary for your domain. Default: Primary. In case you want to setup secondary name servers, you just define IP addresses or master DNS servers for the domain.
After submitting, your domain should be served by OpenStack.
After submitting, your domain should be served by 3Engines.
Step 3 Checking the presence of the domain on the Internet[🔗](#step-3-checking-the-presence-of-the-domain-on-the-internet "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------------------------------------------
@ -228,7 +228,7 @@ www.exampledomain.com. 3600 IN A 64.225.133.254
Step 6 Managing records[🔗](#step-6-managing-records "Permalink to this headline")
---------------------------------------------------------------------------------
Anytime you want to review, edit or delete records in your domain, visit OpenStack dashboard, **Project** → **DNS** → **Zones**. After clicking the domain name of your interest, choose **Record Sets** tab and see the list of all records:
Anytime you want to review, edit or delete records in your domain, visit 3Engines dashboard, **Project** → **DNS** → **Zones**. After clicking the domain name of your interest, choose **Record Sets** tab and see the list of all records:
![show_example_domain_record_sets.png](../_images/show_example_domain_record_sets.png)
@ -237,18 +237,18 @@ From this screen you can update or delete records.
Limitations[🔗](#limitations "Permalink to this headline")
---------------------------------------------------------
There are the following limitations in OpenStack DNSaaS:
There are the following limitations in 3Engines DNSaaS:
> * You cannot manage NS records for your domain. Therefore
>
> > + you cannot add additional secondary name servers
> > + you are unable to delegate subdomains to external servers
> * Even though you are able to configure reverse DNS for your domain, this configuration will have no effect since reverse DNS for 3Engines Cloud IP pools are managed on DNS servers other than OpenStack DNSaaS.
> * Even though you are able to configure reverse DNS for your domain, this configuration will have no effect since reverse DNS for 3Engines Cloud IP pools are managed on DNS servers other than 3Engines DNSaaS.
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
-----------------------------------------------------------------
Once an OpenStack object has floating IP address, you can use the DNS service to propagate a domain name and, thus, create a service or a site. There are several situations in which you can create a floating IP address:
Once an 3Engines object has floating IP address, you can use the DNS service to propagate a domain name and, thus, create a service or a site. There are several situations in which you can create a floating IP address:
You already have an existing VM
: Follow the procedure in article [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md) to assign a new floating IP to it.

2
docs/cloud/Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md
View File

@ -34,4 +34,4 @@ During the VM creation process, while choosing flavor, you may spot a yellow exc
You can expand the flavor summary by clicking the arrow on the left. The charts will show the current free resources as well as the resources that will remain after creating a new instance.
If the quota would be exceeded, OpenStack will non allow to choose this particular flavor.
If the quota would be exceeded, 3Engines will non allow to choose this particular flavor.

6
docs/cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-OpenStack-Dashboard-Horizon-on-3Engines-Cloud.html.md → docs/cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md
View File

@ -1,4 +1,4 @@
How To Create a New Linux VM With NVIDIA Virtual GPU in the OpenStack Dashboard Horizon on 3Engines Cloud[🔗](#how-to-create-a-new-linux-vm-with-nvidia-virtual-gpu-in-the-openstack-dashboard-horizon-on-brand-name "Permalink to this headline")
How To Create a New Linux VM With NVIDIA Virtual GPU in the 3Engines Dashboard Horizon on 3Engines Cloud[🔗](#how-to-create-a-new-linux-vm-with-nvidia-virtual-gpu-in-the-3Engines-dashboard-horizon-on-brand-name "Permalink to this headline")
===================================================================================================================================================================================================================================================
You can create Linux virtual machine with NVIDIA RTX A6000 as the additional graphics card. The card contains
@ -88,7 +88,7 @@ Open “Security Groups” After that, choose “allow\_ping\_ssh\_icmp\_rdp”
![createnew6.png](../_images/createnew6.png)
Choose or generate SSH keypair, as explained in article [How to create key pair in OpenStack Dashboard on 3Engines Cloud](How-to-create-key-pair-in-OpenStack-Dashboard-on-3Engines-Cloud.html.md) for your VM. Next, launch your instance by clicking on blue button.
Choose or generate SSH keypair, as explained in article [How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md) for your VM. Next, launch your instance by clicking on blue button.
![createnew7.png](../_images/createnew7.png)
@ -109,7 +109,7 @@ Open the drop-down menu and choose “Console”.
You can connect to your virtual machine using SSH, see this article: [How to connect to your virtual machine via SSH in Linux on 3Engines Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md)
You can also use the SPICE console using the Openstack Dashboard.
You can also use the SPICE console using the 3Engines Dashboard.
Click on the black terminal area (to activate access to the console). Type:

10
docs/cloud/How-to-access-the-VM-from-OpenStack-console-on-3Engines-Cloud.html.md → docs/cloud/How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md
View File

@ -1,7 +1,7 @@
How to access the VM from OpenStack console on 3Engines Cloud[🔗](#how-to-access-the-vm-from-openstack-console-on-brand-name "Permalink to this headline")
How to access the VM from 3Engines console on 3Engines Cloud[🔗](#how-to-access-the-vm-from-3Engines-console-on-brand-name "Permalink to this headline")
===========================================================================================================================================================
Once you have created a virtual machine in OpenStack, you will need to perform various administrative tasks such as:
Once you have created a virtual machine in 3Engines, you will need to perform various administrative tasks such as:
> * installing and uninstalling software,
> * uploading and downloading files,
@ -72,7 +72,7 @@ You will then use the console as a predefined user called **eouser**.
Attention
Google Chrome seems to work slowly while using the OpenStack console. Firefox works well.
Google Chrome seems to work slowly while using the 3Engines console. Firefox works well.
Using console to perform administrative tasks within Fedora VMs[🔗](#using-console-to-perform-administrative-tasks-within-fedora-vms "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
@ -96,11 +96,11 @@ where *vault* is the namespace within which the pod *vault-0* will be found and
Further explanations of **exec** command are out of scope of this article. The following article will show you how to activate the **kubectl** command after the cluster has been created:
[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud OpenStack Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-OpenStack-Magnum.html.md)
[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md)
This article shows an example of an **exec** command to enter the VM and, later, save the data within it:
[Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on 3Engines Cloud OpenStack Magnum](../kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-3Engines-Cloud-OpenStack-Magnum.html.md)
[Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on 3Engines Cloud 3Engines Magnum](../kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-3Engines-Cloud-3Engines-Magnum.html.md)
### Performing administrative tasks within Windows based VMs[🔗](#performing-administrative-tasks-within-windows-based-vms "Permalink to this headline")

4
docs/cloud/How-to-clone-existing-and-configured-VMs-on-3Engines-Cloud.html.md
View File

@ -1,7 +1,7 @@
How to clone existing and configured VMs on 3Engines Cloud[🔗](#how-to-clone-existing-and-configured-vms-on-brand-name "Permalink to this headline")
=====================================================================================================================================================
The simplest way to create the snapshot of your machine is using “Horizon” - graphical interface of OpenStack dashboard.
The simplest way to create the snapshot of your machine is using “Horizon” - graphical interface of 3Engines dashboard.
In summary, there will be 2 operations:
@ -22,7 +22,7 @@ Once the snapshot is ready, you may see it on **“Images”** page of Horizon.
Now, you may click **“Launch”** in right upper corner of the window or just go back to **“Instances”** menu and launch new instance.
Full manual is here: [How to create new Linux VM in OpenStack Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-OpenStack-Dashboard-Horizon-on-3Engines-Cloud.html.md)
Full manual is here: [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md)
But if this process is familiar to you, there is only one difference. Chose as the source **“boot from snapshot”** instead of **“boot from image”** and select your snapshot from the list below. In next steps select parameters (flavour, size), at least the same as the original one. (“Launch instance” button will be unavailable until all necessary settings were completed).

2
docs/cloud/How-to-create-Windows-VM-on-OpenStack-Horizon-and-access-it-via-web-console-on-3Engines-Cloud.html.md → docs/cloud/How-to-create-Windows-VM-on-3Engines-Horizon-and-access-it-via-web-console-on-3Engines-Cloud.html.md
View File

@ -1,4 +1,4 @@
How to create Windows VM on OpenStack Horizon and access it via web console on 3Engines Cloud[🔗](#how-to-create-windows-vm-on-openstack-horizon-and-access-it-via-web-console-on-brand-name "Permalink to this headline")
How to create Windows VM on 3Engines Horizon and access it via web console on 3Engines Cloud[🔗](#how-to-create-windows-vm-on-3Engines-horizon-and-access-it-via-web-console-on-brand-name "Permalink to this headline")
===========================================================================================================================================================================================================================
This article provides a straightforward way of creating a functional Windows VM on 3Engines Cloud cloud, using the Horizon graphical interface.

14
docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md
View File

@ -50,11 +50,11 @@ No. 4 **SSH client installed and configured on your local Linux computer**
The SSH client must be installed and configured on your local Linux computer. Please see [Generating an SSH keypair in Linux on 3Engines Cloud](../networking/Generating-a-SSH-keypair-in-Linux-on-3Engines-Cloud.html.md).
If you already have an SSH key pair and an SSH client configured, you should import your public key to the Horizon dashboard. The following article contains information how to do it: [How to import SSH public key to OpenStack Horizon on 3Engines Cloud](../networking/How-to-Import-SSH-Public-Key-to-OpenStack-Horizon-on-3Engines-Cloud.html.md).
If you already have an SSH key pair and an SSH client configured, you should import your public key to the Horizon dashboard. The following article contains information how to do it: [How to import SSH public key to 3Engines Horizon on 3Engines Cloud](../networking/How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md).
Alternatively, you can also create a key pair directly in the Horizon:
[How to create key pair in OpenStack Dashboard on 3Engines Cloud](How-to-create-key-pair-in-OpenStack-Dashboard-on-3Engines-Cloud.html.md).
[How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md).
Options for creation of a Virtual Machine (VM)[🔗](#options-for-creation-of-a-virtual-machine-vm "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------------------
@ -63,7 +63,7 @@ Creation of a virtual machine is divided into 11 sections, four of which are man
Note
In OpenStack terminology, a *virtual machine* is also an *instance*. *Instance* is a broader term as not all instances need be virtual machines, it is also possible to use real hardware as an instance.
In 3Engines terminology, a *virtual machine* is also an *instance*. *Instance* is a broader term as not all instances need be virtual machines, it is also possible to use real hardware as an instance.
The window to create a virtual machine is called **Launch Instance**. You will enter all the data about an instance into that window and its options.
@ -110,7 +110,7 @@ You should now see the following form:
![create-linux-linux-07_creodias.png](../_images/create-linux-linux-07_creodias.png)
The standard definition of OpenStack *flavor* is the amount of resources available to the instance - like VCPU, memory and storage capacity.
The standard definition of 3Engines *flavor* is the amount of resources available to the instance - like VCPU, memory and storage capacity.
Choose the one which suits you best and click **↑** next to it.
@ -178,7 +178,7 @@ In the image above, the key is called **test-key**. There are three ways to ente
> * using option **Create Key Pair** – create it on the spot,
> * using option **Import Key Pair** – take the keys you already have and upload them to the cloud,
> * using one of the key pairs that were already existing within OpenStack cloud.
> * using one of the key pairs that were already existing within 3Engines cloud.
If you haven’t created your key pair yet, please follow Prerequisite No. 4.
@ -242,11 +242,11 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
To create a *cluster* of instances, see the series of articles on Kubernetes:
[How to Create a Kubernetes Cluster Using 3Engines Cloud OpenStack Magnum](../kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-OpenStack-Magnum.html.md).
[How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](../kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md).
If you find yourself unable to connect to your virtual machine using SSH, you can use the web console for troubleshooting and other purposes. Here’s how to do it:
[How to access the VM from OpenStack console on 3Engines Cloud](How-to-access-the-VM-from-OpenStack-console-on-3Engines-Cloud.html.md)
[How to access the VM from 3Engines console on 3Engines Cloud](How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md)
If you don’t want the storage of your instance to be deleted while the VM is removed, you can choose to use a volume during instance creation. Please see the following articles:

14
docs/cloud/How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md
View File

@ -60,9 +60,9 @@ No. 5 **SSH key**
You need to have an SSH key pair. It consists of a public and private key. You can use your existing pair in this workflow or create a new one. If you do not have one, you have several options, such as:
* Generate them directly using the Horizon dashboard: [How to create key pair in OpenStack Dashboard on 3Engines Cloud](How-to-create-key-pair-in-OpenStack-Dashboard-on-3Engines-Cloud.html.md).
* Generate them directly using the Horizon dashboard: [How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md).
* Generate your key pair using the Windows command line. Please check this article: [How to Create SSH Key Pair in Windows 10 On 3Engines Cloud](../windows/How-To-Create-SSH-Key-Pair-In-Windows-On-3Engines-Cloud.html.md). If you choose that option, make sure that you upload your public key to the Horizon dashboard: [How to import SSH public key to OpenStack Horizon on 3Engines Cloud](../networking/How-to-Import-SSH-Public-Key-to-OpenStack-Horizon-on-3Engines-Cloud.html.md).
* Generate your key pair using the Windows command line. Please check this article: [How to Create SSH Key Pair in Windows 10 On 3Engines Cloud](../windows/How-To-Create-SSH-Key-Pair-In-Windows-On-3Engines-Cloud.html.md). If you choose that option, make sure that you upload your public key to the Horizon dashboard: [How to import SSH public key to 3Engines Horizon on 3Engines Cloud](../networking/How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md).
This article contains information about configuring PuTTY using one such key pair.
@ -73,7 +73,7 @@ Creation of a virtual machine is divided into 11 sections, four of which are man
Note
In OpenStack terminology, a *virtual machine* is also an *instance*. *Instance* is a broader term as not all instances need be virtual machines, it is also possible to use real hardware as an instance.
In 3Engines terminology, a *virtual machine* is also an *instance*. *Instance* is a broader term as not all instances need be virtual machines, it is also possible to use real hardware as an instance.
The window to create a virtual machine is called **Launch Instance**. You will enter all the data about an instance into that window.
@ -120,7 +120,7 @@ You should now see the following form:
![create-linux-linux-07_creodias.png](../_images/create-linux-linux-07_creodias.png)
The standard definition of OpenStack *flavor* is the amount of resources available to the instance - like VCPU, memory and storage capacity.
The standard definition of 3Engines *flavor* is the amount of resources available to the instance - like VCPU, memory and storage capacity.
Choose the one which suits you best and click **↑** next to it.
@ -193,7 +193,7 @@ In the image above, the key is called **test-key**. There are three ways to ente
> * using option **Create Key Pair** – create it on the spot,
> * using option **Import Key Pair** – take the keys you already have and upload them to the cloud,
> * using one of the key pairs that were already existing within OpenStack cloud.
> * using one of the key pairs that were already existing within 3Engines cloud.
If you haven’t created your key pair yet, please follow Prerequisite No. 5.
@ -354,11 +354,11 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
To create a *cluster* of instances, see the series of articles on Kubernetes:
[How to Create a Kubernetes Cluster Using 3Engines Cloud OpenStack Magnum](../kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-OpenStack-Magnum.html.md).
[How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](../kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md).
If you find yourself unable to connect to your virtual machine using SSH, you can use the web console for troubleshooting and other purposes. Here’s how to do it:
[How to access the VM from OpenStack console on 3Engines Cloud](How-to-access-the-VM-from-OpenStack-console-on-3Engines-Cloud.html.md)
[How to access the VM from 3Engines console on 3Engines Cloud](How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md)
If you don’t want the storage of your instance to be deleted while the VM is removed, you can choose to use a volume during instance creation. Please see the following articles:

18
docs/cloud/How-to-create-a-VM-using-the-OpenStack-CLI-client-on-3Engines-Cloud-cloud.html.md → docs/cloud/How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md
View File

@ -1,12 +1,12 @@
How to create a VM using the OpenStack CLI client on 3Engines Cloud cloud[🔗](#how-to-create-a-vm-using-the-openstack-cli-client-on-brand-name-cloud "Permalink to this headline")
How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud[🔗](#how-to-create-a-vm-using-the-3Engines-cli-client-on-brand-name-cloud "Permalink to this headline")
===================================================================================================================================================================================
This article will cover creating a virtual machine on 3Engines Cloud cloud using the OpenStack CLI client exclusively. It contains basic information to get you started.
This article will cover creating a virtual machine on 3Engines Cloud cloud using the 3Engines CLI client exclusively. It contains basic information to get you started.
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * The **openstack** command to create a VM
> * The **3Engines** command to create a VM
> * Selecting parameters of the new virtual machine
>
> > * Image
@ -26,18 +26,18 @@ No. 1 **Account**
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://horizon.3Engines.com>.
No. 2 **OpenStack CLI client configured**
No. 2 **3Engines CLI client configured**
To have the OpenStack CLI client configured and operational, see article: [How to install OpenStackClient for Linux on 3Engines Cloud](../openstackcli/How-to-install-OpenStackClient-for-Linux-on-3Engines-Cloud.html.md).
To have the 3Engines CLI client configured and operational, see article: [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md).
If the command
```
openstack flavor list
3Engines flavor list
```
shows a list of flavors, the **openstack** command is operational.
shows a list of flavors, the **3Engines** command is operational.
No. 3 **Available image to create a new VM from**
@ -54,14 +54,14 @@ Images that are automatically included on 3Engines Cloud cloud
: There is a set of images that come predefined with the cloud. Typically, that default list of images will contain Ubuntu, CentOS, and Windows 2019/22 images, with various flavors. Other default images could be available as well, say, for AlmaLinux, OPNSense, OSGeolive, Rocky Linux and so on.
Images shared from other projects
: Under OpenStack, images can be shared between the projects. To have an alien image available in your project, you have to accept it first.
: Under 3Engines, images can be shared between the projects. To have an alien image available in your project, you have to accept it first.
Images uploaded within your account
: Finally, you can upload an image by yourself. Once uploaded, the image will be a first class citizen but it may not be automatically available on other accounts you might have.
See this article
[How to upload your custom image using OpenStack CLI on 3Engines Cloud](How-to-upload-your-custom-image-using-OpenStack-CLI-on-3Engines-Cloud.html.md)
[How to upload your custom image using 3Engines CLI on 3Engines Cloud](How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md)
for an example of uploading a new Debian image to the cloud.

2
docs/cloud/How-to-create-instance-snapshot-using-Horizon-on-3Engines-Cloud.html.md
View File

@ -53,7 +53,7 @@ You need a 3Engines Cloud hosting account with access to the Horizon interface:
No. 2 **Ephemeral storage vs. persistent storage**
Please see article [Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in OpenStack.
Please see article [Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in 3Engines.
No. 3 **Instance with ephemeral storage**

2
docs/cloud/How-to-create-key-pair-in-OpenStack-Dashboard-on-3Engines-Cloud.html.md → docs/cloud/How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md
View File

@ -1,4 +1,4 @@
How to create key pair in OpenStack Dashboard on 3Engines Cloud[🔗](#how-to-create-key-pair-in-openstack-dashboard-on-brand-name "Permalink to this headline")
How to create key pair in 3Engines Dashboard on 3Engines Cloud[🔗](#how-to-create-key-pair-in-3Engines-dashboard-on-brand-name "Permalink to this headline")
===============================================================================================================================================================
Open **Compute -> Key Pairs**

4
docs/cloud/How-to-create-new-Linux-VM-in-OpenStack-Dashboard-Horizon-on-3Engines-Cloud.html.md → docs/cloud/How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md
View File

@ -1,4 +1,4 @@
How to create new Linux VM in OpenStack Dashboard Horizon on 3Engines Cloud[🔗](#how-to-create-new-linux-vm-in-openstack-dashboard-horizon-on-brand-name "Permalink to this headline")
How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud[🔗](#how-to-create-new-linux-vm-in-3Engines-dashboard-horizon-on-brand-name "Permalink to this headline")
=======================================================================================================================================================================================
Go to **Project → Compute → Instances**.
@ -31,7 +31,7 @@ Open **“Security Groups”** After that, choose “default” and “allow\_pi
![newvm6.png](../_images/newvm6.png)
Choose or generate SSH keypair [How to create key pair in OpenStack Dashboard on 3Engines Cloud](How-to-create-key-pair-in-OpenStack-Dashboard-on-3Engines-Cloud.html.md) for your VM. Next, launch your instance by clicking on blue button.
Choose or generate SSH keypair [How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md) for your VM. Next, launch your instance by clicking on blue button.
![newvm7.png](../_images/newvm7.png)

2
docs/cloud/How-to-fix-unresponsive-console-issue-on-3Engines-Cloud.html.md
View File

@ -3,7 +3,7 @@ How to fix unresponsive console issue on 3Engines Cloud[🔗](#how-to-fix-unresp
When you create a new virtual machine, the first thing you might want to do is to have a look at the console panel and check whether the instance has booted correctly.
After opening up the console in OpenStack you might encounter this error:
After opening up the console in 3Engines you might encounter this error:
* unresponsive grey screen
* document icon in the down-right corner which informs about the issue on client side

4
docs/cloud/How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md
View File

@ -17,8 +17,8 @@ No. 1 **Hosting**
You need a 3Engines Cloud hosting account with access to Horizon interface: <https://horizon.3Engines.com>
No. 2 **OpenStack CLI client installed and configured**
No. 2 **3Engines CLI client installed and configured**
You need to have the OpenStack CLI operational.
You need to have the 3Engines CLI operational.
First, it must be installed. You have several options, such as:

44
docs/cloud/How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md
View File

@ -14,20 +14,20 @@ You need a 3Engines Cloud hosting account with Horizon interface <https://horizo
No. 2 **Authenticate**
Once you have installed this piece of software, you need to authenticate to start using it: [How to activate OpenStack CLI access to 3Engines Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-OpenStack-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md)
Once you have installed this piece of software, you need to authenticate to start using it: [How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md)
No. 3 **OpenStackClient installed and available**
No. 3 **3EnginesClient installed and available**
OpenStack is written in Python, it is recommended to use a dedicated virtual environment for the rest of this article.
3Engines is written in Python, it is recommended to use a dedicated virtual environment for the rest of this article.
Install GitBash on Windows
: [How to install OpenStackClient GitBash for Windows on 3Engines Cloud](../openstackcli/How-to-install-OpenStackClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md).
: [How to install 3EnginesClient GitBash for Windows on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md).
Install and run WSL (Linux under Windows)
: [How to install OpenStackClient on Windows using Windows Subsystem for Linux on 3Engines Cloud OpenStack Hosting](../openstackcli/How-to-install-OpenStackClient-on-Windows-using-Windows-Subsystem-for-Linux-on-3Engines-Cloud-OpenStack-Hosting.html.md).
: [How to install 3EnginesClient on Windows using Windows Subsystem for Linux on 3Engines Cloud 3Engines Hosting](../3Enginescli/How-to-install-3EnginesClient-on-Windows-using-Windows-Subsystem-for-Linux-on-3Engines-Cloud-3Engines-Hosting.html.md).
Install OpenStackClient on Linux
: [How to install OpenStackClient for Linux on 3Engines Cloud](../openstackcli/How-to-install-OpenStackClient-for-Linux-on-3Engines-Cloud.html.md).
Install 3EnginesClient on Linux
: [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md).
No. 4 **jq installed and running**
@ -46,7 +46,7 @@ Step 1 CLI Commands for Application Credentials[🔗](#step-1-cli-commands-for-a
Command
```
openstack application credential
3Engines application credential
```
@ -63,7 +63,7 @@ application credential show
To see the parameters for these commands, end them with **--help**, like this:
```
openstack application credential create --help
3Engines application credential create --help
```
@ -81,7 +81,7 @@ Step 2 The Simplest Way to Create a New Application Credential[🔗](#step-2-the
The simplest way to generate a new application credential is just to define the name – the rest of the parameters will be defined automatically for you. The following command uses name **cred2**:
```
openstack application credential create cred2
3Engines application credential create cred2
```
@ -109,7 +109,7 @@ _member_ magnum_user load-balancer_member heat_stack_owner creator k8s_admin
Note
Role **\_member\_** is the most basic role and should always be present. Beware however, as in some variations of OpenStack it can be called **member** instead of **\_member\_**.
Role **\_member\_** is the most basic role and should always be present. Beware however, as in some variations of 3Engines it can be called **member** instead of **\_member\_**.
**--expiration**
@ -134,7 +134,7 @@ By default, for security reasons, application credentials are forbidden from bei
Here is a complete example, using all of the available parameters to create a new application credential:
```
openstack application credential create foo-dev-member4 --role _member_ --expiration $(date +"%Y-11-%dT%H:%M:%S") --description "Test application credentials" --unrestricted -c id -c secret -f json | jq -r '"application_credential_id: \"" + .id + "\"", "application_credential_secret: \"" + .secret + "\""'
3Engines application credential create foo-dev-member4 --role _member_ --expiration $(date +"%Y-11-%dT%H:%M:%S") --description "Test application credentials" --unrestricted -c id -c secret -f json | jq -r '"application_credential_id: \"" + .id + "\"", "application_credential_secret: \"" + .secret + "\""'
```
@ -147,7 +147,7 @@ The name of the new application credential will be **foo-dev-member4**, will be
Step 4 Enter id and secret into clouds.yml[🔗](#step-4-enter-id-and-secret-into-clouds-yml "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------------
You are now going to store the values of **id** and **secret** that the cloud has sent to you. Once stored, future **openstack** commands will use these value to authenticate to the cloud without using any kind of password.
You are now going to store the values of **id** and **secret** that the cloud has sent to you. Once stored, future **3Engines** commands will use these value to authenticate to the cloud without using any kind of password.
The place to store *id* and *secret* is a file called *clouds.yml*. It may reside on your local computer in one of these three locations:
@ -159,14 +159,14 @@ Current directory
The current directory is searched first.
User configuration directory
: **$HOME/.config/openstack/clouds.yml**
: **$HOME/.config/3Engines/clouds.yml**
The most common default location for individual users.
Searched after the current directory.
System-wide configuration directory
: **/etc/openstack/clouds.yml**
: **/etc/3Engines/clouds.yml**
Searches that location as the last resort.
@ -181,7 +181,7 @@ The contents of the *clouds.yml* file will be in *yaml* format. It is customary
Let us create a new application credential called *trial-member\_creatornew*.
```
openstack application credential create trial-member_creatornew --unrestricted -c id -c secret -f json | jq -r '"application_credential_id: \"" + .id + "\"", "application_credential_secret: \"" + .secret + "\""'
3Engines application credential create trial-member_creatornew --unrestricted -c id -c secret -f json | jq -r '"application_credential_id: \"" + .id + "\"", "application_credential_secret: \"" + .secret + "\""'
```
@ -192,7 +192,7 @@ This is the result:
Now create the *clouds.yml* file using your preferred editor of choice. Here it is *nano*:
```
nano $HOME/.config/openstack/clouds.yml
nano $HOME/.config/3Engines/clouds.yml
```
@ -217,7 +217,7 @@ Let us dissect that file line by line:
> * **trial-member\_creatornew** is the name of the application credential used in the previous *credential create* command.
> * **v3applicationcredential** is the type of auth connection (it is always the same)
> * **auth** start of *auth* parameters
> * **auth\_url** the address to call on the 3Engines Cloud OpenStack server (it always the same)
> * **auth\_url** the address to call on the 3Engines Cloud 3Engines server (it always the same)
> * **application\_credential\_id** the value from the previous call of *credential create* command
> * **credential create** command the value from the previous call of *credential create* command
@ -254,7 +254,7 @@ It works.
You can also use that parameter in the command line, like this:
```
openstack --os-cloud=trial-member_creatornew flavor list
3Engines --os-cloud=trial-member_creatornew flavor list
```
@ -262,7 +262,7 @@ It works as well:
![cli_os_cloud.png](../_images/cli_os_cloud.png)
You have to set up **OS\_CLOUD** once per opening a new terminal window and then you can use **openstack** command without interpolating **--os-cloud** parameter all the time.
You have to set up **OS\_CLOUD** once per opening a new terminal window and then you can use **3Engines** command without interpolating **--os-cloud** parameter all the time.
If you had two or more clouds defined in the *clouds.yml* file, then using **--os-cloud** in the command line would be more flexible.
@ -301,6 +301,6 @@ Here are some articles that use application credentials:
[How to install Rancher RKE2 Kubernetes on 3Engines Cloud](../kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-3Engines-Cloud-cloud.html.md)
[Configuring IP Whitelisting for OpenStack Load Balancer using Terraform on 3Engines Cloud](../kubernetes/Configuring-IP-Whitelisting-for-OpenStack-Load-Balancer-using-Terraform-on-3Engines-Cloud.html.md)
[Configuring IP Whitelisting for 3Engines Load Balancer using Terraform on 3Engines Cloud](../kubernetes/Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Terraform-on-3Engines-Cloud.html.md)
[OpenStack User Roles on 3Engines Cloud](OpenStack-user-roles-on-3Engines-Cloud.html.md)
[3Engines User Roles on 3Engines Cloud](3Engines-user-roles-on-3Engines-Cloud.html.md)

4
docs/cloud/How-to-start-a-VM-from-a-snapshot-on-3Engines-Cloud.html.md
View File

@ -32,7 +32,7 @@ a) Volume Snapshot[🔗](#a-volume-snapshot "Permalink to this headline")
![snap7.png](../_images/snap7.png)
8. The rest of procedure is the same: [How to create new Linux VM in OpenStack Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-OpenStack-Dashboard-Horizon-on-3Engines-Cloud.html.md).
8. The rest of procedure is the same: [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md).
9. Newly created machine is visible in the Instances list.
@ -66,7 +66,7 @@ In the “Images” you may also find symbolic links to the volume snapshots.(i.
![snap5.png](../_images/snap5.png)
6. The rest of procedure is the same: [How to create new Linux VM in OpenStack Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-OpenStack-Dashboard-Horizon-on-3Engines-Cloud.html.md).
6. The rest of procedure is the same: [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md).
7. Virtual machine has been created.

2
docs/cloud/How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-3Engines-Cloud.html.md
View File

@ -12,7 +12,7 @@ You need a 3Engines Cloud hosting account with access to the Horizon interface:
No. 2 **Ephemeral storage vs. persistent storage**
Please see article [Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in OpenStack.
Please see article [Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in 3Engines.
No. 3 **Instance snapshot**

8
docs/cloud/How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-3Engines-Cloud.html.md
View File

@ -1,7 +1,7 @@
How to transfer volumes between domains and projects using Horizon dashboard on 3Engines Cloud[🔗](#how-to-transfer-volumes-between-domains-and-projects-using-horizon-dashboard-on-brand-name "Permalink to this headline")
=============================================================================================================================================================================================================================
Volumes in OpenStack can be used to store data. They are visible to virtual machines like drives.
Volumes in 3Engines can be used to store data. They are visible to virtual machines like drives.
Such a volume is usually available to just the project in which it was created. Transferring data stored on it between projects might take a long time, especially if such a volume contains lots of data, like, say, hundreds or thousands of gigabytes (or even more).
@ -33,7 +33,7 @@ You can check the status of your volume in the **Volumes -> Volumes** section of
![transfer-volume-between-projects-horizon-32_creodias.png](../_images/transfer-volume-between-projects-horizon-32_creodias.png)
The following article includes information how to disconnect a volume from a virtual machine: [How to move data volume between two VMs using OpenStack Horizon on 3Engines Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-OpenStack-Horizon-on-3Engines-Cloud.html.md)
The following article includes information how to disconnect a volume from a virtual machine: [How to move data volume between two VMs using 3Engines Horizon on 3Engines Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-3Engines-Horizon-on-3Engines-Cloud.html.md)
No. 4 **Ability to perform operations on both the source project and the destination project**
@ -141,6 +141,6 @@ After cancelling, your volume should now once again have status **Available**:
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
-----------------------------------------------------------------
Now that the volume has been transferred, you might want to connect it to a virtual machine. This article includes information how to do that: [How to move data volume between two VMs using OpenStack Horizon on 3Engines Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-OpenStack-Horizon-on-3Engines-Cloud.html.md)
Now that the volume has been transferred, you might want to connect it to a virtual machine. This article includes information how to do that: [How to move data volume between two VMs using 3Engines Horizon on 3Engines Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-3Engines-Horizon-on-3Engines-Cloud.html.md)
The workflow described in this article can also be done using the OpenStack CLI. Learn more here: [How to transfer volumes between domains and projects using OpenStack CLI client on 3Engines Cloud](../openstackcli/How-to-transfer-volumes-between-domains-and-projects-using-OpenStack-CLI-client-on-3Engines-Cloud.html.md)
The workflow described in this article can also be done using the 3Engines CLI. Learn more here: [How to transfer volumes between domains and projects using 3Engines CLI client on 3Engines Cloud](../3Enginescli/How-to-transfer-volumes-between-domains-and-projects-using-3Engines-CLI-client-on-3Engines-Cloud.html.md)

4
docs/cloud/How-to-upload-custom-image-to-3Engines-Cloud-cloud-using-OpenStack-Horizon-dashboard.html.md → docs/cloud/How-to-upload-custom-image-to-3Engines-Cloud-cloud-using-3Engines-Horizon-dashboard.html.md
View File

@ -1,4 +1,4 @@
How to upload custom image to 3Engines Cloud cloud using OpenStack Horizon dashboard[🔗](#how-to-upload-custom-image-to-brand-name-cloud-using-openstack-horizon-dashboard "Permalink to this headline")
How to upload custom image to 3Engines Cloud cloud using 3Engines Horizon dashboard[🔗](#how-to-upload-custom-image-to-brand-name-cloud-using-3Engines-horizon-dashboard "Permalink to this headline")
=========================================================================================================================================================================================================
In this tutorial, you will upload custom image stored on your local computer to 3Engines Cloud cloud, using the Horizon Dashboard. The uploaded image will be available within your project alongside default images from 3Engines Cloud cloud and you will be able to create virtual machines using it.
@ -35,7 +35,7 @@ The following container formats are supported:
> | aki | ami | ari | bare |
> | docker | ova | ovf | |
For the explanation of these formats, see article [What Image Formats are Available in OpenStack 3Engines Cloud cloud](What-Image-Formats-are-available-in-OpenStack-3Engines-Cloud-Cloud.html.md).
For the explanation of these formats, see article [What Image Formats are Available in 3Engines 3Engines Cloud cloud](What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md).
No. 3 **Uploaded public SSH key**

12
docs/cloud/How-to-upload-your-custom-image-using-OpenStack-CLI-on-3Engines-Cloud.html.md → docs/cloud/How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md
View File

@ -1,12 +1,12 @@
How to upload your custom image using OpenStack CLI on 3Engines Cloud[🔗](#how-to-upload-your-custom-image-using-openstack-cli-on-brand-name "Permalink to this headline")
How to upload your custom image using 3Engines CLI on 3Engines Cloud[🔗](#how-to-upload-your-custom-image-using-3Engines-cli-on-brand-name "Permalink to this headline")
===========================================================================================================================================================================
In this tutorial, you will upload custom image stored on your local computer to 3Engines Cloud cloud, using the OpenStack CLI client. The uploaded image will be available within your project alongside default images from 3Engines Cloud cloud and you will be able to create virtual machines using it.
In this tutorial, you will upload custom image stored on your local computer to 3Engines Cloud cloud, using the 3Engines CLI client. The uploaded image will be available within your project alongside default images from 3Engines Cloud cloud and you will be able to create virtual machines using it.
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * How to check for the presence of the image in your OpenStack cloud
> * How to check for the presence of the image in your 3Engines cloud
> * How different images might behave
> * How to upload the image using only CLI commands
> * Example: how to upload image for Debian 11
@ -19,9 +19,9 @@ No. 1 **Account**
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://horizon.3Engines.com>.
No. 2 **OpenStack CLI configured**
No. 2 **3Engines CLI configured**
You need to have the OpenStack CLI client configured and operational. See [How to install OpenStackClient for Linux on 3Engines Cloud](../openstackcli/How-to-install-OpenStackClient-for-Linux-on-3Engines-Cloud.html.md). You can test whether your OpenStack CLI is properly activated by executing the **openstack server list** command mentioned in the end of that article - it should return the list of your virtual machines.
You need to have the 3Engines CLI client configured and operational. See [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md). You can test whether your 3Engines CLI is properly activated by executing the **3Engines server list** command mentioned in the end of that article - it should return the list of your virtual machines.
No. 3 **Custom image you wish to upload**
@ -39,7 +39,7 @@ The following container formats are supported:
> | aki | ami | ari | bare |
> | docker | ova | ovf | |
For the explanation of these formats, see article [What Image Formats are Available in OpenStack 3Engines Cloud cloud](What-Image-Formats-are-available-in-OpenStack-3Engines-Cloud-Cloud.html.md).
For the explanation of these formats, see article [What Image Formats are Available in 3Engines 3Engines Cloud cloud](What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md).
No. 4 **Uploaded public SSH key**

2
docs/cloud/How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md
View File

@ -1,7 +1,7 @@
How to use Security Groups in Horizon on 3Engines Cloud[🔗](#how-to-use-security-groups-in-horizon-on-brand-name "Permalink to this headline")
===============================================================================================================================================
Security groups in **OpenStack** are used to filter the Internet traffic coming **to** and **from** your virtual machines. They consist of security rules and can be attached to your virtual machines during and after the creation of the machines.
Security groups in **3Engines** are used to filter the Internet traffic coming **to** and **from** your virtual machines. They consist of security rules and can be attached to your virtual machines during and after the creation of the machines.
By default, each instance has a rule which blocks all incoming Internet traffic and allows all outgoing traffic. To modify those settings, you can apply other security groups to it.

10
docs/cloud/Resizing-a-virtual-machine-using-OpenStack-Horizon-on-3Engines-Cloud.html.md → docs/cloud/Resizing-a-virtual-machine-using-3Engines-Horizon-on-3Engines-Cloud.html.md
View File

@ -1,10 +1,10 @@
Resizing a virtual machine using OpenStack Horizon on 3Engines Cloud[🔗](#resizing-a-virtual-machine-using-openstack-horizon-on-brand-name "Permalink to this headline")
Resizing a virtual machine using 3Engines Horizon on 3Engines Cloud[🔗](#resizing-a-virtual-machine-using-3Engines-horizon-on-brand-name "Permalink to this headline")
=========================================================================================================================================================================
Introduction[🔗](#introduction "Permalink to this headline")
-----------------------------------------------------------
When creating a new virtual machine under OpenStack, one of the options you choose is the *flavor*. A flavor is a predefined combination of CPU, memory and disk size and there usually is a number of such flavors for you to choose from.
When creating a new virtual machine under 3Engines, one of the options you choose is the *flavor*. A flavor is a predefined combination of CPU, memory and disk size and there usually is a number of such flavors for you to choose from.
After the instance is spawned, it is possible to change one flavor for another, and that process is called *resizing*. You might want to resize an already existing VM in order to:
@ -14,7 +14,7 @@ After the instance is spawned, it is possible to change one flavor for another,
> * seamlessly transition from testing to production environment,
> * change application workload byt scaling the VM up or down.
In this article, we are going to resize VMs using commands in OpenStack Horizon.
In this article, we are going to resize VMs using commands in 3Engines Horizon.
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
@ -39,7 +39,7 @@ Also:
> * The VM you want to resize is in an active or shut down state.
> * A flavor with the desired resource configuration exists.
> * Adequate resources are available in your OpenStack environment to accommodate the resize.
> * Adequate resources are available in your 3Engines environment to accommodate the resize.
Creating a new VM[🔗](#creating-a-new-vm "Permalink to this headline")
---------------------------------------------------------------------
@ -131,4 +131,4 @@ In this case, the sizes of the disk before and after the resizing do not match.
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
-----------------------------------------------------------------
You can also resize the virtual machine using only OpenStack CLI. More details here: [Resizing a virtual machine using OpenStack CLI on 3Engines Cloud](../openstackcli/Resizing-a-virtual-machine-using-OpenStack-CLI-on-3Engines-Cloud.html.md)
You can also resize the virtual machine using only 3Engines CLI. More details here: [Resizing a virtual machine using 3Engines CLI on 3Engines Cloud](../3Enginescli/Resizing-a-virtual-machine-using-3Engines-CLI-on-3Engines-Cloud.html.md)

4
docs/cloud/Spot-instances-on-3Engines-Cloud.html.md
View File

@ -27,6 +27,6 @@ No. 3 **Using quotas and flavors**
For quotas, see this article: [Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md)
No. 3 **OpenStack CLI client**
No. 3 **3Engines CLI client**
If you want to interact with 3Engines Cloud cloud using OpenStack CLI client, you need to have it installed. Check one of these articles:
If you want to interact with 3Engines Cloud cloud using 3Engines CLI client, you need to have it installed. Check one of these articles:

2
docs/cloud/Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-3Engines-Cloud.html.md
View File

@ -1,7 +1,7 @@
Status Power State and dependencies in billing of instance VMs on 3Engines Cloud[🔗](#status-power-state-and-dependencies-in-billing-of-instance-vms-on-brand-name "Permalink to this headline")
=================================================================================================================================================================================================
In OpenStack, instances have their own Status and Power State:
In 3Engines, instances have their own Status and Power State:
> * **Status** informs about the present condition of the VM, while
> * **Power** states tell us only whether virtual machines are running or not.

8
docs/cloud/What-Image-Formats-are-available-in-OpenStack-3Engines-Cloud-Cloud.html.md → docs/cloud/What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md
View File

@ -1,15 +1,15 @@
What Image Formats are Available in OpenStack 3Engines Cloud cloud[🔗](#what-image-formats-are-available-in-openstack-brand-name-cloud "Permalink to this headline")
What Image Formats are Available in 3Engines 3Engines Cloud cloud[🔗](#what-image-formats-are-available-in-3Engines-brand-name-cloud "Permalink to this headline")
=====================================================================================================================================================================
In 3Engines Cloud OpenStack ten image format extensions are available:
In 3Engines Cloud 3Engines ten image format extensions are available:
**QCOW2** - Formatted Virtual Machine Storage is a storage format for virtual machine disk images. QCOW stands for “QEMU copy on write”. It is used with the KVM hypervisor. The images are typically smaller than RAW images, so it is often faster to convert a raw image to qcow2 for uploading instead of uploading the raw file directly. Because raw images do not support snapshots, OpenStack Compute will automatically convert raw image files to qcow2 as needed.
**QCOW2** - Formatted Virtual Machine Storage is a storage format for virtual machine disk images. QCOW stands for “QEMU copy on write”. It is used with the KVM hypervisor. The images are typically smaller than RAW images, so it is often faster to convert a raw image to qcow2 for uploading instead of uploading the raw file directly. Because raw images do not support snapshots, 3Engines Compute will automatically convert raw image files to qcow2 as needed.
**RAW** - The RAW storage is the simplest one, and is natively supported by both KVM and Xen hypervisors. RAW image could be considered as the bit-equivalent of a block device file. It has a performance advantage over QCOW2 in that no formatting is applied to virtual machine disk images stored in the RAW format. No additional work from hosts is required in Virtual machine data operations on disk images stored in this format.
**ISO** - The ISO format is a disk image formatted with the read-only ISO 9660 filesystem which is used for CDs and DVDs. While ISO is not frequently considered as a virtual machine image format, because of ISOs contain bootable filesystems with an installed operating system, it can be treated like other virtual machine image files.
**VDI** - Virtual Disk Image format used by VirtualBox for image files. None of the OpenStack Compute hypervisors supports VDI directly, so it will be needed to convert these files to a different format to use them.
**VDI** - Virtual Disk Image format used by VirtualBox for image files. None of the 3Engines Compute hypervisors supports VDI directly, so it will be needed to convert these files to a different format to use them.
**VHD** - Virtual Hard Disk format for images, widely used by Microsoft (e.g. Hyper-V, Microsoft Virtual PC).

8
docs/cloud/What-is-an-OpenStack-domain-on-3Engines-Cloud.html.md → docs/cloud/What-is-an-3Engines-domain-on-3Engines-Cloud.html.md
View File

@ -1,9 +1,9 @@
What is an OpenStack domain on 3Engines Cloud[🔗](#what-is-an-openstack-domain-on-brand-name "Permalink to this headline")
What is an 3Engines domain on 3Engines Cloud[🔗](#what-is-an-3Engines-domain-on-brand-name "Permalink to this headline")
===========================================================================================================================
**Domain**
Intention of providing a domain in cloud environment is to define boundaries for management. OpenStack domain is a type of a container for projects, users and groups.
Intention of providing a domain in cloud environment is to define boundaries for management. 3Engines domain is a type of a container for projects, users and groups.
One crucial benefit is separating overlapping resource names for different domains.
Furthermore, permissions in the project and domain are two not related things, hereby customization for administrator is made up much easier.
@ -17,10 +17,10 @@ You cannot create a new domain.
**Service relation**
3Engines Cloud account is linked to your main account in particular domain, hence it allows you to login to the OpenStack dashboard without any need to deliver keystone credentials.
3Engines Cloud account is linked to your main account in particular domain, hence it allows you to login to the 3Engines dashboard without any need to deliver keystone credentials.
This type of facility is due to a proper implementation of KeyCloak and KeyStone relation.
**Docs**
Click here if you want to see official [OpenStack documentation for domains](https://docs.openstack.org/security-guide/identity/domains.html.md).
Click here if you want to see official [3Engines documentation for domains](https://docs.3Engines.org/security-guide/identity/domains.html.md).

10
docs/cloud/What-is-an-OpenStack-project-on-3Engines-Cloud.html.md → docs/cloud/What-is-an-3Engines-project-on-3Engines-Cloud.html.md
View File

@ -1,22 +1,22 @@
What is an OpenStack project on 3Engines Cloud[🔗](#what-is-an-openstack-project-on-brand-name "Permalink to this headline")
What is an 3Engines project on 3Engines Cloud[🔗](#what-is-an-3Engines-project-on-brand-name "Permalink to this headline")
=============================================================================================================================
A **project** is a isolated group of zero or more users who share common access with specific privileges to the software instance in OpenStack. A project is created for each set of instances and networks that are configured as a discrete entity for the project. In Compute, a project owns virtual machines (in Compute) or containers (in Object Storage).
A **project** is a isolated group of zero or more users who share common access with specific privileges to the software instance in 3Engines. A project is created for each set of instances and networks that are configured as a discrete entity for the project. In Compute, a project owns virtual machines (in Compute) or containers (in Object Storage).
You can imagine that the whole OpenStack cloud is a big cake of resources (vCPU, disks, instances, etc…) and projects are the pieces of this cake served to the customers.
You can imagine that the whole 3Engines cloud is a big cake of resources (vCPU, disks, instances, etc…) and projects are the pieces of this cake served to the customers.
Current project name is **visible** in the Horizon panel.
![project1.png](../_images/project1.png)
Projects are created, managed, and edited at the OpenStack **Projects** screen.
Projects are created, managed, and edited at the 3Engines **Projects** screen.
![project2.png](../_images/project2.png)
Users can be associated with more than one project, but once signed, they can only see and access the resources available in that project.
Each project and user pairing can have a role associated with it.
OpenStack users can create projects, and create new accounts using the OpenStack Dashboard. They can also associate other users with roles, projects, or both.
3Engines users can create projects, and create new accounts using the 3Engines Dashboard. They can also associate other users with roles, projects, or both.
To remove project its mandatory to manually remove all of its resources first.

26
docs/cloud/cloud.html.md
View File

@ -3,36 +3,36 @@
## Available Documentation
* [Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md)
* [How to access the VM from OpenStack console on 3Engines Cloud](How-to-access-the-VM-from-OpenStack-console-on-3Engines-Cloud.html.md)
* [How to access the VM from 3Engines console on 3Engines Cloud](How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md)
* [How to clone existing and configured VMs on 3Engines Cloud](How-to-clone-existing-and-configured-VMs-on-3Engines-Cloud.html.md)
* [How to fix unresponsive console issue on 3Engines Cloud](How-to-fix-unresponsive-console-issue-on-3Engines-Cloud.html.md)
* [How to generate and manage EC2 credentials on 3Engines Cloud](How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md)
* [How to generate or use Application Credentials via CLI on 3Engines Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md)
* [How to Use GUI in Linux VM on 3Engines Cloud and access it From Local Linux Computer](How-to-use-GUI-in-Linux-VM-on-3Engines-Cloud-and-access-it-from-local-Linux-computer.html.md)
* [How To Create a New Linux VM With NVIDIA Virtual GPU in the OpenStack Dashboard Horizon on 3Engines Cloud](How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-OpenStack-Dashboard-Horizon-on-3Engines-Cloud.html.md)
* [How To Create a New Linux VM With NVIDIA Virtual GPU in the 3Engines Dashboard Horizon on 3Engines Cloud](How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md)
* [How to install and use Docker on Ubuntu 24.04](How-to-use-Docker-on-3Engines-Cloud.html.md)
* [How to use Security Groups in Horizon on 3Engines Cloud](How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md)
* [How to create key pair in OpenStack Dashboard on 3Engines Cloud](How-to-create-key-pair-in-OpenStack-Dashboard-on-3Engines-Cloud.html.md)
* [How to create new Linux VM in OpenStack Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-OpenStack-Dashboard-Horizon-on-3Engines-Cloud.html.md)
* [How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md)
* [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md)
* [How to install Python virtualenv or virtualenvwrapper on 3Engines Cloud](How-to-install-Python-virtualenv-or-virtualenvwrapper-on-3Engines-Cloud.html.md)
* [How to start a VM from a snapshot on 3Engines Cloud](How-to-start-a-VM-from-a-snapshot-on-3Engines-Cloud.html.md)
* [Status Power State and dependencies in billing of instance VMs on 3Engines Cloud](Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-3Engines-Cloud.html.md)
* [How to upload your custom image using OpenStack CLI on 3Engines Cloud](How-to-upload-your-custom-image-using-OpenStack-CLI-on-3Engines-Cloud.html.md)
* [How to upload your custom image using 3Engines CLI on 3Engines Cloud](How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md)
* [VM created with option Create New Volume No on 3Engines Cloud](VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md)
* [VM created with option Create New Volume Yes on 3Engines Cloud](VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md)
* [What is an OpenStack domain on 3Engines Cloud](What-is-an-OpenStack-domain-on-3Engines-Cloud.html.md)
* [What is an OpenStack project on 3Engines Cloud](What-is-an-OpenStack-project-on-3Engines-Cloud.html.md)
* [What is an 3Engines domain on 3Engines Cloud](What-is-an-3Engines-domain-on-3Engines-Cloud.html.md)
* [What is an 3Engines project on 3Engines Cloud](What-is-an-3Engines-project-on-3Engines-Cloud.html.md)
* [How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md)
* [How to create a Linux VM and access it from Linux command line on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md)
* [DNS as a Service on 3Engines Cloud Hosting](DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md)
* [What Image Formats are Available in OpenStack 3Engines Cloud cloud](What-Image-Formats-are-available-in-OpenStack-3Engines-Cloud-Cloud.html.md)
* [How to upload custom image to 3Engines Cloud cloud using OpenStack Horizon dashboard](How-to-upload-custom-image-to-3Engines-Cloud-cloud-using-OpenStack-Horizon-dashboard.html.md)
* [How to create Windows VM on OpenStack Horizon and access it via web console on 3Engines Cloud](How-to-create-Windows-VM-on-OpenStack-Horizon-and-access-it-via-web-console-on-3Engines-Cloud.html.md)
* [What Image Formats are Available in 3Engines 3Engines Cloud cloud](What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md)
* [How to upload custom image to 3Engines Cloud cloud using 3Engines Horizon dashboard](How-to-upload-custom-image-to-3Engines-Cloud-cloud-using-3Engines-Horizon-dashboard.html.md)
* [How to create Windows VM on 3Engines Horizon and access it via web console on 3Engines Cloud](How-to-create-Windows-VM-on-3Engines-Horizon-and-access-it-via-web-console-on-3Engines-Cloud.html.md)
* [How to transfer volumes between domains and projects using Horizon dashboard on 3Engines Cloud](How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-3Engines-Cloud.html.md)
* [Spot instances on 3Engines Cloud](Spot-instances-on-3Engines-Cloud.html.md)
* [How to create instance snapshot using Horizon on 3Engines Cloud](How-to-create-instance-snapshot-using-Horizon-on-3Engines-Cloud.html.md)
* [How to start a VM from instance snapshot using Horizon dashboard on 3Engines Cloud](How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-3Engines-Cloud.html.md)
* [How to create a VM using the OpenStack CLI client on 3Engines Cloud cloud](How-to-create-a-VM-using-the-OpenStack-CLI-client-on-3Engines-Cloud-cloud.html.md)
* [OpenStack User Roles on 3Engines Cloud](OpenStack-user-roles-on-3Engines-Cloud.html.md)
* [Resizing a virtual machine using OpenStack Horizon on 3Engines Cloud](Resizing-a-virtual-machine-using-OpenStack-Horizon-on-3Engines-Cloud.html.md)
* [How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud](How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md)
* [3Engines User Roles on 3Engines Cloud](3Engines-user-roles-on-3Engines-Cloud.html.md)
* [Resizing a virtual machine using 3Engines Horizon on 3Engines Cloud](Resizing-a-virtual-machine-using-3Engines-Horizon-on-3Engines-Cloud.html.md)
* [Block storage and object storage performance limits on 3Engines Cloud](Block-storage-and-object-storage-performance-limits-on-3Engines-Cloud.html.md)