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

link icon replaced

Browse Source
This commit is contained in:
govardhan
2025-06-19 14:09:10 +05:30
parent 60adbde60c
commit 172f8e2b34
158 changed files with 996 additions and 996 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/cloud/Block-storage-and-object-storage-performance-limits-on-CloudFerro-Cloud.html.md
View File

@ -1,9 +1,9 @@
Block storage and object storage performance limits on CloudFerro Cloud[](#block-storage-and-object-storage-performance-limits-on-brand-name "Permalink to this headline")
Block storage and object storage performance limits on CloudFerro Cloud[🔗](#block-storage-and-object-storage-performance-limits-on-brand-name "Permalink to this headline")
===========================================================================================================================================================================
On CloudFerro Cloud, there are performance limits for **HDD**, **NVMe (SSD)**, and **Object Storage** to ensure stable operation and protect against accidental DDoS attacks.
Current limits[](#current-limits "Permalink to this headline")
Current limits[🔗](#current-limits "Permalink to this headline")
---------------------------------------------------------------
Block HDD

22
docs/cloud/DNS-as-a-Service-on-CloudFerro-Cloud-Hosting.html.md
View File

@ -1,4 +1,4 @@
DNS as a Service on CloudFerro Cloud Hosting[](#dns-as-a-service-on-brand-name-cloud-name-hosting "Permalink to this headline")
DNS as a Service on CloudFerro Cloud Hosting[🔗](#dns-as-a-service-on-brand-name-cloud-name-hosting "Permalink to this headline")
================================================================================================================================
DNS as a Service (DNSaaS) provides functionality of managing configuration of user’s domains. Managing configuration means that the user is capable of creating, updating and deleting the following DNS records:
@ -22,7 +22,7 @@ DNS records management is performed on the level of an OpenStack 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.
What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this headline")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * Domain delegation in registrar’s system
@ -33,7 +33,7 @@ What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this h
> * Managing records
> * Limitations in OpenStack DNSaaS
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**
@ -71,7 +71,7 @@ Or, you might connect from a Linux based computer to the cloud:
In both cases, the article will contain a section to connect floating IP to the newly created VM. The generated IP address will vary, but for the sake of concreteness we shall assume that it is **64.225.133.254**. You will enter that value later in this article, to create record set for the site or service you are making.
Step 1 Delegate domain to your registrar’s system[](#step-1-delegate-domain-to-your-registrar-s-system "Permalink to this headline")
Step 1 Delegate domain to your registrar’s system[🔗](#step-1-delegate-domain-to-your-registrar-s-system "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------------------------
The configuration of domain name in your registrar’s system must point to the NS records of CloudFerro name servers. It can be achieved in two ways:
@ -102,7 +102,7 @@ Configure glue records for your domain, so that they point to the following IP a
| secondary name server | ns2.exampledomain.com | 91.212.141.102 |
| secondary name server | ns3.exampledomain.com | 91.212.141.86 |
Step 2 Zone configuration[](#step-2-zone-configuration "Permalink to this headline")
Step 2 Zone configuration[🔗](#step-2-zone-configuration "Permalink to this headline")
-------------------------------------------------------------------------------------
Zone configuration is defining parameters for the main domain name you have purchased.
@ -121,7 +121,7 @@ Here is what the parameters mean:
After submitting, your domain should be served by OpenStack.
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")
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")
-------------------------------------------------------------------------------------------------------------------------------------------------------
It usually takes from 24 up to 48 hours for the domain name to propagate through the Internet so it will **not** be available right away. Rarely, domain name starts resolving in matters of minutes and hours instead of days, so it pays to try the domain address in your browser an hour or two after configuring the zone for the domain.
@ -170,7 +170,7 @@ curl exampledomain.com
Specify **A** to see the propagation of the domain itself and specify **NS** to see the propagation of nameservers across the Internet.
Step 4 Adding new record for the domain[](#step-4-adding-new-record-for-the-domain "Permalink to this headline")
Step 4 Adding new record for the domain[🔗](#step-4-adding-new-record-for-the-domain "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------
To add a new record to the domain, click on **Create Record Set** next to the domain name and fill in the required fields. The most important entry is to connect the domain name to the IP address you have. To configure an address of web server in **exampledomain.com**, so that it is resolved to **64.225.133.254** which is a Floating IP address of your server, fill the form as follows:
@ -206,7 +206,7 @@ Note
Each time a name of domain or a server is added or edited, add dot ‘.’ at the end of the entry.
For example: **exampledomain.com.** or **mail.exampledomain.com.**.
Step 5 Adding records for subdomains[](#step-5-adding-records-for-subdomains "Permalink to this headline")
Step 5 Adding records for subdomains[🔗](#step-5-adding-records-for-subdomains "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------
Defining subdomains is similar except that, normally, the subdomain would propagate within minutes instead of days.
@ -225,7 +225,7 @@ www.exampledomain.com. 3600 IN A 64.225.133.254
```
Step 6 Managing records[](#step-6-managing-records "Permalink to this headline")
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:
@ -234,7 +234,7 @@ Anytime you want to review, edit or delete records in your domain, visit OpenSta
From this screen you can update or delete records.
Limitations[](#limitations "Permalink to this headline")
Limitations[🔗](#limitations "Permalink to this headline")
---------------------------------------------------------
There are the following limitations in OpenStack DNSaaS:
@ -245,7 +245,7 @@ There are the following limitations in OpenStack DNSaaS:
> > + 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 CloudFerro Cloud IP pools are managed on DNS servers other than OpenStack DNSaaS.
What To Do Next[](#what-to-do-next "Permalink to this headline")
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:

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

@ -1,4 +1,4 @@
Dashboard Overview – Project Quotas And Flavors Limits on CloudFerro Cloud[](#dashboard-overview-project-quotas-and-flavors-limits-on-brand-name "Permalink to this headline")
Dashboard Overview – Project Quotas And Flavors Limits on CloudFerro Cloud[🔗](#dashboard-overview-project-quotas-and-flavors-limits-on-brand-name "Permalink to this headline")
===============================================================================================================================================================================
While using CloudFerro Cloud platform, one of the first things you will spot is the “Limit Summary”. Each project is restricted by preset quotas. This is preventing system capacities from being exhausted without notification and guaranteeing free resources.

12
docs/cloud/How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-OpenStack-Dashboard-Horizon-on-CloudFerro-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 CloudFerro 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 OpenStack Dashboard Horizon on CloudFerro Cloud[🔗](#how-to-create-a-new-linux-vm-with-nvidia-virtual-gpu-in-the-openstack-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
@ -9,7 +9,7 @@ You can create Linux virtual machine with NVIDIA RTX A6000 as the additional gra
There are four variants, using 6, 12, 24, or 48 GB of VGPU RAM. You will be able to select the particular model by choosing a proper flavor when creating the instance in Horizon (see below).
What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this headline")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * How to create an instance with NVIDIA support
@ -19,7 +19,7 @@ What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this h
> * use the console within Horizon interface and
> * verify that you are using the NVIDIA vGPU.
Step 1 Create New Instance with NVIDIA Image Support[](#step-1-create-new-instance-with-nvidia-image-support "Permalink to this headline")
Step 1 Create New Instance with NVIDIA Image Support[🔗](#step-1-create-new-instance-with-nvidia-image-support "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------------------------------
To define a new instance, use the following series of commands:
@ -58,7 +58,7 @@ Click on the Next button and get to the following screen:
You will now choose one of the four models of the RTX A6000 card.
Step 2 Select Card Model / Flavor[](#step-2-select-card-model-flavor "Permalink to this headline")
Step 2 Select Card Model / Flavor[🔗](#step-2-select-card-model-flavor "Permalink to this headline")
---------------------------------------------------------------------------------------------------
The four available: **RTXA6000-6C**, **RTXA6000-12C**, **RTXA6000-24C**, and **RTXA6000-48C**, are described in this table:
@ -77,7 +77,7 @@ Yellow triangles in the listing mean that you cannot select that row as one of t
In the situation above, select *vm.a6000.2* and continue going through the usual motions of selecting instance elements to finish the procedure.
Step 3 Finish Creating the Instance[](#step-3-finish-creating-the-instance "Permalink to this headline")
Step 3 Finish Creating the Instance[🔗](#step-3-finish-creating-the-instance "Permalink to this headline")
---------------------------------------------------------------------------------------------------------
Click “Networks” and then choose desired networks.
@ -100,7 +100,7 @@ Note
If you want to make your VM accessible from the Internet, see this article: [How to Add or Remove Floating IP’s to your VM on CloudFerro Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-CloudFerro-Cloud.html.md)
Step 4 Issue Commands from the Console[](#step-4-issue-commands-from-the-console "Permalink to this headline")
Step 4 Issue Commands from the Console[🔗](#step-4-issue-commands-from-the-console "Permalink to this headline")
---------------------------------------------------------------------------------------------------------------
Open the drop-down menu and choose “Console”.

12
docs/cloud/How-to-access-the-VM-from-OpenStack-console-on-CloudFerro-Cloud.html.md
View File

@ -1,4 +1,4 @@
How to access the VM from OpenStack console on CloudFerro Cloud[](#how-to-access-the-vm-from-openstack-console-on-brand-name "Permalink to this headline")
How to access the VM from OpenStack console on CloudFerro Cloud[🔗](#how-to-access-the-vm-from-openstack-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:
@ -20,21 +20,21 @@ and so on. There are three ways to enter the back end part of virtual machines:
As these images are only used for automatic creation of Kubernetes instances, you have to enter them using Kubernetes methods. That boils down to using **kubectl exec** command (see below).
What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this headline")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * Use console for Linux based virtual machines
> * Use console for Windows based virtual machines
> * Use console for Fedora base virtual machines
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**
You need a CloudFerro Cloud hosting account with access to the Horizon interface: <https://horizon.cloudferro.com>.
Using console for administrative tasks within Linux based VMs[](#using-console-for-administrative-tasks-within-linux-based-vms "Permalink to this headline")
Using console for administrative tasks within Linux based VMs[🔗](#using-console-for-administrative-tasks-within-linux-based-vms "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------------------------------------------------
1. Go to <https://horizon.cloudferro.com> and select your authentication method:
@ -74,7 +74,7 @@ Attention
Google Chrome seems to work slowly while using the OpenStack 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")
Using console to perform administrative tasks within Fedora VMs[🔗](#using-console-to-perform-administrative-tasks-within-fedora-vms "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
For normal VMs, choose either Ubuntu- or CentOS-based images while creating a VM – but not Fedora. It is meant only for automatic creation of instances that belong to Kubernetes clusters. Such instances will have either word *master* or *node* in their names. Here is a typical series of instances that belong to two different clusters, called *vault* and *k8s-23*:
@ -102,7 +102,7 @@ This article shows an example of an **exec** command to enter the VM and, later,
[Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on CloudFerro Cloud OpenStack Magnum](../kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-CloudFerro-Cloud-OpenStack-Magnum.html.md)
### Performing administrative tasks within Windows based VMs[](#performing-administrative-tasks-within-windows-based-vms "Permalink to this headline")
### Performing administrative tasks within Windows based VMs[🔗](#performing-administrative-tasks-within-windows-based-vms "Permalink to this headline")
In case of **Windows** set a new password for *Administrator* profile.

2
docs/cloud/How-to-clone-existing-and-configured-VMs-on-CloudFerro-Cloud.html.md
View File

@ -1,4 +1,4 @@
How to clone existing and configured VMs on CloudFerro Cloud[](#how-to-clone-existing-and-configured-vms-on-brand-name "Permalink to this headline")
How to clone existing and configured VMs on CloudFerro 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.

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

@ -1,4 +1,4 @@
How to create Windows VM on OpenStack Horizon and access it via web console on CloudFerro 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 OpenStack Horizon and access it via web console on CloudFerro Cloud[🔗](#how-to-create-windows-vm-on-openstack-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 CloudFerro Cloud cloud, using the Horizon graphical interface.
@ -10,7 +10,7 @@ The idea is to
all from your Internet browser.
What Are We Going To Cover[](#what-are-we-going-to-cover "Permalink to this headline")
What Are We Going To Cover[🔗](#what-are-we-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * Accessing the Launch Instance menu
@ -22,14 +22,14 @@ What Are We Going To Cover[](#what-are-we-going-to-cover "Permalink to this h
> * Launching virtual machine
> * Setting **Administrator** password
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**
You need a CloudFerro Cloud hosting account with access to the Horizon interface: <https://horizon.cloudferro.com>.
Step 1: Access the Launch Instance menu[](#step-1-access-the-launch-instance-menu "Permalink to this headline")
Step 1: Access the Launch Instance menu[🔗](#step-1-access-the-launch-instance-menu "Permalink to this headline")
----------------------------------------------------------------------------------------------------------------
In the Horizon dashboard, navigate to **Compute -> Instances**. Click the **Launch Instance** at the top of the **Instances** section:
@ -40,7 +40,7 @@ You should get the following window:
![create-windows-vm-horizon-web-console-02_creodias.png](../_images/create-windows-vm-horizon-web-console-02_creodias.png)
Step 2: Choose the instance name[](#step-2-choose-the-instance-name "Permalink to this headline")
Step 2: Choose the instance name[🔗](#step-2-choose-the-instance-name "Permalink to this headline")
--------------------------------------------------------------------------------------------------
In the window which appeared, enter the name you wish to give to your instance in the **Instance Name** text field. In this example, we use **test-windows-vm** as the name:
@ -49,7 +49,7 @@ In the window which appeared, enter the name you wish to give to your instance i
Click **Next >**.
Step 3: Choose source[](#step-3-choose-source "Permalink to this headline")
Step 3: Choose source[🔗](#step-3-choose-source "Permalink to this headline")
----------------------------------------------------------------------------
The default value in the drop-down menu **Select Boot Source** is **Image**, meaning that you will choose from one of the images that are present in your version of Horizon. If another value is selected, revert to **Image** instead.
@ -72,7 +72,7 @@ Click **Next >**.
If you allocate a wrong image by mistake, you can remove it from the **Allocated** section by clicking **↓** next to its name.
Step 4: Choose flavor[](#step-4-choose-flavor "Permalink to this headline")
Step 4: Choose flavor[🔗](#step-4-choose-flavor "Permalink to this headline")
----------------------------------------------------------------------------
In this step you will choose the flavor of your virtual machine. Flavors manage access to resources such as VCPUS, RAM and storage.
@ -119,7 +119,7 @@ Note
In examples that follow, we use two networks, one with name starting with **cloud\_** and the name of the other starting with **eodata\_**. The former network should always be present in the account, but the latter may or may not present. If you do not have network which name starts with **eodata\_**, you may create it or use any other network that you already have and want to use.
Step 5: Attach networks to your virtual machine[](#step-5-attach-networks-to-your-virtual-machine "Permalink to this headline")
Step 5: Attach networks to your virtual machine[🔗](#step-5-attach-networks-to-your-virtual-machine "Permalink to this headline")
--------------------------------------------------------------------------------------------------------------------------------
The next step contains the list of networks available to you:
@ -135,7 +135,7 @@ Allocate both of them and click **Next >**.
The next step is called **Network Ports**. In it simply quick **Next >** without doing anything else.
Step 6: Choose security groups[](#step-6-choose-security-groups "Permalink to this headline")
Step 6: Choose security groups[🔗](#step-6-choose-security-groups "Permalink to this headline")
----------------------------------------------------------------------------------------------
Security groups control Internet traffic for your virtual machine.
@ -146,7 +146,7 @@ Group **allow\_ping\_ssh\_icmp\_rdp** exposes your VM to various types of networ
![create-windows-vm-horizon-web-console-11_creodias.png](../_images/create-windows-vm-horizon-web-console-11_creodias.png)
Step 7: Launch your virtual machine[](#step-7-launch-your-virtual-machine "Permalink to this headline")
Step 7: Launch your virtual machine[🔗](#step-7-launch-your-virtual-machine "Permalink to this headline")
--------------------------------------------------------------------------------------------------------
Other steps from the **Launch Instance** window are optional. Once you have done the previous steps of this article, click **Launch Instance** button:
@ -159,7 +159,7 @@ Your virtual machine should appear in the **Instances** section of the Horizon d
Once the **Status** is **Active**, the virtual machine should be running. The next step involves setting access to it.
Step 8: Set the Administrator password[](#step-8-set-the-administrator-password "Permalink to this headline")
Step 8: Set the Administrator password[🔗](#step-8-set-the-administrator-password "Permalink to this headline")
--------------------------------------------------------------------------------------------------------------
Once your instance has **Active** status, click on its name:
@ -194,7 +194,7 @@ Click **OK**.
Wait until you see the standard Windows desktop.
Step 9: Update Windows[](#step-9-update-windows "Permalink to this headline")
Step 9: Update Windows[🔗](#step-9-update-windows "Permalink to this headline")
------------------------------------------------------------------------------
Once the Windows virtual machine is up and running, you should update its operating system to have the latest security fixes. Click **Start**, and then **Settings**:
@ -211,7 +211,7 @@ You should now see **Windows Update** screen, which can look like this:
Follow the appropriate prompts to update your operating system.
What To Do Next[](#what-to-do-next "Permalink to this headline")
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
-----------------------------------------------------------------
If you want to access your virtual machine remotely using RDP (Remote Desktop Protocol), you should consider increasing its security by using a bastion host. The following article contains more information: [Connecting to a Windows VM via RDP through a Linux bastion host port forwarding on CloudFerro Cloud](../windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-CloudFerro-Cloud.html.md)

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

@ -1,4 +1,4 @@
How to create a Linux VM and access it from Linux command line on CloudFerro Cloud[](#how-to-create-a-linux-vm-and-access-it-from-linux-command-line-on-brand-name "Permalink to this headline")
How to create a Linux VM and access it from Linux command line on CloudFerro Cloud[🔗](#how-to-create-a-linux-vm-and-access-it-from-linux-command-line-on-brand-name "Permalink to this headline")
=================================================================================================================================================================================================
Creating a virtual machine in a CloudFerro Cloud cloud allows you to perform computations without having to engage your own infrastructure. In this article you shall create a Linux based virtual machine and access it remotely from a Linux command line on a desktop or laptop.
@ -9,7 +9,7 @@ Note
This article only covers the basics of creating a VM - it does not cover topics such as use of NVIDIA hardware or creating a volume during the creation of a VM.
What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this headline")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * Creating a Linux virtual machine in CloudFerro Cloud cloud using command **Launch Instance** from Horizon Dashboard
@ -31,7 +31,7 @@ For external access
> * Attach a floating IP to the instance so that it can be found on the Internet and, finally,
> * Use SSH to connect to that virtual machine from another Linux based system
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Hosting**
@ -56,7 +56,7 @@ Alternatively, you can also create a key pair directly in the Horizon:
[How to create key pair in OpenStack Dashboard on CloudFerro Cloud](How-to-create-key-pair-in-OpenStack-Dashboard-on-CloudFerro-Cloud.html.md).
Options for creation of a Virtual Machine (VM)[](#options-for-creation-of-a-virtual-machine-vm "Permalink to this headline")
Options for creation of a Virtual Machine (VM)[🔗](#options-for-creation-of-a-virtual-machine-vm "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------------------
Creation of a virtual machine is divided into 11 sections, four of which are mandatory (denoted by an asterisk in the end of the name of the option). In addition to those four (**Details**, **Source**, **Flavor**, and **Networks**), we shall define **Security Groups** and **Key Pairs**. The rest of the options to launch an instance is out of scope of this article.
@ -67,7 +67,7 @@ In OpenStack terminology, a *virtual machine* is also an *instance*. *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.
Step 1 Start the Launch Instance window and name the virtual machine[](#step-1-start-the-launch-instance-window-and-name-the-virtual-machine "Permalink to this headline")
Step 1 Start the Launch Instance window and name the virtual machine[🔗](#step-1-start-the-launch-instance-window-and-name-the-virtual-machine "Permalink to this headline")
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
In the Horizon dashboard go to **Compute** -> **Instances** and click **Launch Instance**. You should get the following window:
@ -78,7 +78,7 @@ Type the name for your virtual machine in the **Instance Name** text field.
Click **Next** or the **Source** option on the left side menu.
Step 2 Define the source of the virtual machine[](#step-2-define-the-source-of-the-virtual-machine "Permalink to this headline")
Step 2 Define the source of the virtual machine[🔗](#step-2-define-the-source-of-the-virtual-machine "Permalink to this headline")
---------------------------------------------------------------------------------------------------------------------------------
The **Source** window appears:
@ -103,7 +103,7 @@ Also, make sure that in the section **Create New Volume** option **No** is selec
Click **Next** or click on button **Flavor** to define the flavor of the instance.
Step 3 Define the flavor of the instance[](#step-3-define-the-flavor-of-the-instance "Permalink to this headline")
Step 3 Define the flavor of the instance[🔗](#step-3-define-the-flavor-of-the-instance "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------
You should now see the following form:
@ -134,7 +134,7 @@ Another possible explanation might be that your quota is too low for creating a
Click **Next** or click **Networks** to define networks.
Step 4 Define networks for the virtual machine[](#step-4-define-networks-for-the-virtual-machine "Permalink to this headline")
Step 4 Define networks for the virtual machine[🔗](#step-4-define-networks-for-the-virtual-machine "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------------------
You should now see the following window:
@ -149,7 +149,7 @@ Choose that network and also choose any other network that you want to access th
These were the obligatory options. Since you want to access the instance through an SSH connection, you will need to define **Security Groups** and **Key Pair**.
Step 5 Define security groups for VM[](#step-5-define-security-groups-for-vm "Permalink to this headline")
Step 5 Define security groups for VM[🔗](#step-5-define-security-groups-for-vm "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------
Security groups control network traffic to and from your virtual machine.
@ -165,7 +165,7 @@ By default, you have access to two groups:
Enable both of these rules. One of the open ports in **allow\_ping\_ssh\_icmp\_rdp** is 22, which is a prerequisite for SSH access.
Step 6 Create a key pair for SSH access[](#step-6-create-a-key-pair-for-ssh-access "Permalink to this headline")
Step 6 Create a key pair for SSH access[🔗](#step-6-create-a-key-pair-for-ssh-access "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------
To use SSH to connect your local Linux computer to the cloud Linux “computer”, you will need to provide one public and one secret key. (Keys are random strings, usually hundreds of characters long.)
@ -184,7 +184,7 @@ If you haven’t created your key pair yet, please follow Prerequisite No. 4.
Anyways, make sure that your uploaded key is in the **Allocated** section.
Step 7 Create the instance[](#step-7-create-the-instance "Permalink to this headline")
Step 7 Create the instance[🔗](#step-7-create-the-instance "Permalink to this headline")
---------------------------------------------------------------------------------------
Once you have set everything up, click **Launch Instance**.
@ -205,7 +205,7 @@ In Step 4 you have attached a network with the name that starts with **cloud\_**
Just like on the above screenshot, under header **IP Address**, you will see network addresses which both start with **10.**. It means that they are local network addresses. If you want to access your instance remotely, it must have a static IP address. The way to add it is to attach a so-called *floating IP* address to the instance.
Step 8 Attach a Floating IP to the instance[](#step-8-attach-a-floating-ip-to-the-instance "Permalink to this headline")
Step 8 Attach a Floating IP to the instance[🔗](#step-8-attach-a-floating-ip-to-the-instance "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------------
Here is how to create and attach a floating IP to your instance: [How to Add or Remove Floating IP’s to your VM on CloudFerro Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-CloudFerro-Cloud.html.md).
@ -216,7 +216,7 @@ Once you have added the floating IP, you will see it in the Horizon dashboard un
The floating IP address in that article is **64.225.132.0**. Your address will vary.
Step 9 Connecting to your virtual machine using SSH[](#step-9-connecting-to-your-virtual-machine-using-ssh "Permalink to this headline")
Step 9 Connecting to your virtual machine using SSH[🔗](#step-9-connecting-to-your-virtual-machine-using-ssh "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------------------------------
The following article has information about connecting to a virtual machine using SSH: [How to connect to your virtual machine via SSH in Linux on CloudFerro Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-CloudFerro-Cloud.html.md).
@ -230,7 +230,7 @@ ssh [email protected]
The IP address in that article is **64.225.132.99** and is different from the address from the previous article. Instead of IP addresses used in these articles (**64.225.132.99** and **64.225.132.0**), enter the IP address of your instance which you saw after doing Step 8.
What To Do Next[](#what-to-do-next "Permalink to this headline")
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
-----------------------------------------------------------------
CloudFerro Cloud cloud can be used for general hosting needs, such as

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

@ -1,4 +1,4 @@
How to create a Linux VM and access it from Windows desktop on CloudFerro Cloud[](#how-to-create-a-linux-vm-and-access-it-from-windows-desktop-on-brand-name "Permalink to this headline")
How to create a Linux VM and access it from Windows desktop on CloudFerro Cloud[🔗](#how-to-create-a-linux-vm-and-access-it-from-windows-desktop-on-brand-name "Permalink to this headline")
===========================================================================================================================================================================================
Creating a virtual machine in a CloudFerro Cloud cloud allows you to perform computations without having to engage your own infrastructure. In this article you shall create a Linux based virtual machine and access it remotely using PuTTY on Windows.
@ -9,7 +9,7 @@ Note
This article only covers the basics of creating a VM - it does not cover topics such as use of NVIDIA hardware or creating a volume during the creation of a VM.
What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this headline")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * Creating a Linux virtual machine in CloudFerro Cloud cloud using command **Launch Instance** from Horizon Dashboard
@ -37,7 +37,7 @@ After that, you will connect to a VM using PuTTY:
> * Save PuTTY configuration
> * Connect to a VM
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Hosting**
@ -66,7 +66,7 @@ You need to have an SSH key pair. It consists of a public and private key. You c
This article contains information about configuring PuTTY using one such key pair.
Options for creation of a Virtual Machine (VM)[](#options-for-creation-of-a-virtual-machine-vm "Permalink to this headline")
Options for creation of a Virtual Machine (VM)[🔗](#options-for-creation-of-a-virtual-machine-vm "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------------------
Creation of a virtual machine is divided into 11 sections, four of which are mandatory (denoted by an asterisk in the end of the name of the option). In addition to those four (**Details**, **Source**, **Flavor**, and **Networks**), we shall define **Security Groups** and **Key Pairs**. The rest of the options to launch an instance is out of scope of this article.
@ -77,7 +77,7 @@ In OpenStack terminology, a *virtual machine* is also an *instance*. *Instance*
The window to create a virtual machine is called **Launch Instance**. You will enter all the data about an instance into that window.
Step 1 Start the Launch Instance window and name the virtual machine[](#step-1-start-the-launch-instance-window-and-name-the-virtual-machine "Permalink to this headline")
Step 1 Start the Launch Instance window and name the virtual machine[🔗](#step-1-start-the-launch-instance-window-and-name-the-virtual-machine "Permalink to this headline")
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
In the Horizon dashboard go to **Compute** -> **Instances** and click **Launch Instance**. You should get the following window:
@ -88,7 +88,7 @@ Type the name for your virtual machine in the **Instance Name** text field.
Click **Next** or the **Source** option on the left side menu.
Step 2 Define the source of the virtual machine[](#step-2-define-the-source-of-the-virtual-machine "Permalink to this headline")
Step 2 Define the source of the virtual machine[🔗](#step-2-define-the-source-of-the-virtual-machine "Permalink to this headline")
---------------------------------------------------------------------------------------------------------------------------------
The **Source** window appears:
@ -113,7 +113,7 @@ Also, make sure that in the section **Create New Volume** option **No** is selec
Click **Next** or click on button **Flavor** to define the flavor of the instance.
Step 3 Define the flavor of the instance[](#step-3-define-the-flavor-of-the-instance "Permalink to this headline")
Step 3 Define the flavor of the instance[🔗](#step-3-define-the-flavor-of-the-instance "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------
You should now see the following form:
@ -146,7 +146,7 @@ Another possible cause might be that your quota is too low for creating a VM wit
Click **Next** or click **Networks** to define networks.
Step 4 Define networks for the virtual machine[](#step-4-define-networks-for-the-virtual-machine "Permalink to this headline")
Step 4 Define networks for the virtual machine[🔗](#step-4-define-networks-for-the-virtual-machine "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------------------
You should now see a window to choose one or several networks that you want your VM to work with:
@ -164,7 +164,7 @@ Other networks may be present in the system.
These were the obligatory options. Since you want to access the instance through an SSH connection, you will need to define **Security Groups** and **Key Pair**.
Step 5 Define security groups for VM[](#step-5-define-security-groups-for-vm "Permalink to this headline")
Step 5 Define security groups for VM[🔗](#step-5-define-security-groups-for-vm "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------
Security groups control network traffic to and from your virtual machine.
@ -180,7 +180,7 @@ By default, you have access to two groups:
Enable both of these rules. One of the open ports in **allow\_ping\_ssh\_icmp\_rdp** is 22, which is a prerequisite for SSH access.
Step 6 Create a key pair for SSH access[](#step-6-create-a-key-pair-for-ssh-access "Permalink to this headline")
Step 6 Create a key pair for SSH access[🔗](#step-6-create-a-key-pair-for-ssh-access "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------
To use SSH to connect your local Linux computer to the cloud Linux “computer”, you will need to provide one public and one secret key. (Keys are random strings, usually hundreds of characters long.)
@ -199,7 +199,7 @@ If you haven’t created your key pair yet, please follow Prerequisite No. 5.
Anyways, make sure that your uploaded key is in the **Allocated** section.
Step 7 Create the instance[](#step-7-create-the-instance "Permalink to this headline")
Step 7 Create the instance[🔗](#step-7-create-the-instance "Permalink to this headline")
---------------------------------------------------------------------------------------
Once you have set everything up, click **Launch Instance**.
@ -220,7 +220,7 @@ In Step 4 you have attached a network with the name that starts with **cloud\_**
Just like on the above screenshot, under header **IP Address**, you will see network addresses which both start with **10.**. It means that they are local network addresses. If you want to access your instance remotely, it must have a static IP address. The way to add it is to attach a so-called *floating IP* address to the instance.
Step 8 Attach a Floating IP to the instance[](#step-8-attach-a-floating-ip-to-the-instance "Permalink to this headline")
Step 8 Attach a Floating IP to the instance[🔗](#step-8-attach-a-floating-ip-to-the-instance "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------------
Here is how to create and attach a floating IP to your instance: [How to Add or Remove Floating IP’s to your VM on CloudFerro Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-CloudFerro-Cloud.html.md).
@ -231,7 +231,7 @@ Once you have added the floating IP, you will see it in the Horizon dashboard un
The floating IP address in that article is **64.225.132.0**. Your address will vary.
Step 9 Convert your SSH key[](#step-9-convert-your-ssh-key "Permalink to this headline")
Step 9 Convert your SSH key[🔗](#step-9-convert-your-ssh-key "Permalink to this headline")
-----------------------------------------------------------------------------------------
If you followed Prequisite No. 5, you should have an SSH key pair on your local computer - public and private.
@ -274,7 +274,7 @@ Close the **PuTTY Key Generator** window. Your saved file should like like this:
Of course, your file will probably have a different name than the one on the screenshot above.
Step 10 Configure PuTTY[](#step-10-configure-putty "Permalink to this headline")
Step 10 Configure PuTTY[🔗](#step-10-configure-putty "Permalink to this headline")
---------------------------------------------------------------------------------
Run **PuTTY** from your **Start** menu. The following window should appear:
@ -297,7 +297,7 @@ The location of your key should appear in the **Private key file for authenticat
![key-location-putty.png](../_images/key-location-putty.png)
Step 11 Save the session settings[](#step-11-save-the-session-settings "Permalink to this headline")
Step 11 Save the session settings[🔗](#step-11-save-the-session-settings "Permalink to this headline")
-----------------------------------------------------------------------------------------------------
To save these settings for future use, return to the **Session** category in which you typed the floating IP of your virtual machine. Choose the name of your session and type it in the text field found in the **Load, save or delete a stored session**:
@ -308,7 +308,7 @@ Click **Save**. Your saved session should appear on the list:
![putty-13.png](../_images/putty-13.png)
Step 12 Connect to your virtual machine[](#step-12-connect-to-your-virtual-machine "Permalink to this headline")
Step 12 Connect to your virtual machine[🔗](#step-12-connect-to-your-virtual-machine "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------
To connect to your virtual machine, click **Open**. If you are connecting to that machine for the first time, you should receive the following alert:
@ -331,7 +331,7 @@ You should now be connected to your virtual machine and be able to execute comma
![putty-16.png](../_images/putty-16.png)
Using your saved PuTTY session to simplify login[](#using-your-saved-putty-session-to-simplify-login "Permalink to this headline")
Using your saved PuTTY session to simplify login[🔗](#using-your-saved-putty-session-to-simplify-login "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------------------------
In order to use your saved session, open **PuTTY**. In the **Load, save or delete a stored session**, click the name of your saved session from the list and click **Load**.
@ -342,7 +342,7 @@ All your settings, including the floating IP of your VM should now be provided:
You can now start your session as explained in Step 12 above.
What To Do Next[](#what-to-do-next "Permalink to this headline")
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
-----------------------------------------------------------------
CloudFerro Cloud cloud can be used for general hosting needs, such as

6
docs/cloud/How-to-create-a-VM-using-the-OpenStack-CLI-client-on-CloudFerro-Cloud-cloud.html.md
View File

@ -1,9 +1,9 @@
How to create a VM using the OpenStack CLI client on CloudFerro 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 OpenStack CLI client on CloudFerro Cloud cloud[🔗](#how-to-create-a-vm-using-the-openstack-cli-client-on-brand-name-cloud "Permalink to this headline")
===================================================================================================================================================================================
This article will cover creating a virtual machine on CloudFerro Cloud cloud using the OpenStack 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")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * The **openstack** command to create a VM
@ -19,7 +19,7 @@ What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this h
> * Adding a floating IP to the existing VM
> * Using SSH to access the VM
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**

8
docs/cloud/How-to-create-instance-snapshot-using-Horizon-on-CloudFerro-Cloud.html.md
View File

@ -1,4 +1,4 @@
How to create instance snapshot using Horizon on CloudFerro Cloud[](#how-to-create-instance-snapshot-using-horizon-on-brand-name "Permalink to this headline")
How to create instance snapshot using Horizon on CloudFerro Cloud[🔗](#how-to-create-instance-snapshot-using-horizon-on-brand-name "Permalink to this headline")
===============================================================================================================================================================
In this article, you will learn how to create instance snapshot on CloudFerro Cloud cloud, using Horizon dashboard.
@ -12,7 +12,7 @@ Instance snapshots allow you to archive the state of the virtual machine. You ca
We cover both types of storage for instances, *ephemeral* and *persistent*.
The plan[](#the-plan "Permalink to this headline")
The plan[🔗](#the-plan "Permalink to this headline")
---------------------------------------------------
In reality, you will be using the procedures described in this article with the already existing instances.
@ -25,7 +25,7 @@ It goes without saying that after following a section about one type of virtual
Or you can keep them and use them to create an instance out of it using one of articles mentioned in What To Do Next.
What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this headline")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * Create snapshot of instance which uses ephemeral storage
@ -44,7 +44,7 @@ What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this h
> + What happens if there are multiple volumes?
> * Downloading an instance snapshot
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**

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

@ -1,4 +1,4 @@
How to create key pair in OpenStack Dashboard on CloudFerro Cloud[](#how-to-create-key-pair-in-openstack-dashboard-on-brand-name "Permalink to this headline")
How to create key pair in OpenStack Dashboard on CloudFerro Cloud[🔗](#how-to-create-key-pair-in-openstack-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-CloudFerro-Cloud.html.md
View File

@ -1,4 +1,4 @@
How to create new Linux VM in OpenStack Dashboard Horizon on CloudFerro 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 OpenStack Dashboard Horizon on CloudFerro Cloud[🔗](#how-to-create-new-linux-vm-in-openstack-dashboard-horizon-on-brand-name "Permalink to this headline")
=======================================================================================================================================================================================
Go to **Project → Compute → Instances**.
@ -43,7 +43,7 @@ Open the drop-down menu and choose **“Console”**.
![newvm9.png](../_images/newvm9.png)
Fig. 2 Click on the black terminal area (to activate access to the console). Type: **eoconsole** and hit Enter.[](#id1 "Permalink to this image")
Fig. 2 Click on the black terminal area (to activate access to the console). Type: **eoconsole** and hit Enter.[🔗](#id1 "Permalink to this image")
![newvm10.png](../_images/newvm10.png)

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

@ -1,4 +1,4 @@
How to fix unresponsive console issue on CloudFerro Cloud[](#how-to-fix-unresponsive-console-issue-on-brand-name "Permalink to this headline")
How to fix unresponsive console issue on CloudFerro Cloud[🔗](#how-to-fix-unresponsive-console-issue-on-brand-name "Permalink to this headline")
===============================================================================================================================================
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.

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

@ -1,4 +1,4 @@
How to generate and manage EC2 credentials on CloudFerro Cloud[](#how-to-generate-and-manage-ec2-credentials-on-brand-name "Permalink to this headline")
How to generate and manage EC2 credentials on CloudFerro Cloud[🔗](#how-to-generate-and-manage-ec2-credentials-on-brand-name "Permalink to this headline")
=========================================================================================================================================================
EC2 credentials are used for accessing private S3 buckets on CloudFerro Cloud cloud. This article covers how to generate and manage a pair of EC2 credentials so that you will be able to mount those buckets both
@ -10,7 +10,7 @@ Warning
A pair of EC2 credentials usually provides access to secret data so share it only with trusted individuals.
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Hosting**

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

@ -1,11 +1,11 @@
How to generate or use Application Credentials via CLI on CloudFerro Cloud[](#how-to-generate-or-use-application-credentials-via-cli-on-brand-name "Permalink to this headline")
How to generate or use Application Credentials via CLI on CloudFerro Cloud[🔗](#how-to-generate-or-use-application-credentials-via-cli-on-brand-name "Permalink to this headline")
=================================================================================================================================================================================
You can authenticate your applications to *keystone* by creating application credentials for them. It is also possible to delegate a subset of role assignments on a project to an application credential, granting the same or restricted authorization to a project for the app.
With application credentials, apps authenticate with the “application credential ID” and a “secret” string which is not the user’s password. Thanks to this, the user’s password is not embedded in the application’s configuration, which is especially important for users whose identities are managed by an external system such as LDAP or a single sign-on system.
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Hosting**
@ -40,7 +40,7 @@ jq --version # Check the installed jq version
```
Step 1 CLI Commands for Application Credentials[](#step-1-cli-commands-for-application-credentials "Permalink to this headline")
Step 1 CLI Commands for Application Credentials[🔗](#step-1-cli-commands-for-application-credentials "Permalink to this headline")
---------------------------------------------------------------------------------------------------------------------------------
Command
@ -75,7 +75,7 @@ Note
The **--help** option will produce a *vim*-like output, so type **q** on the keyboard to get back to the usual terminal line.
Step 2 The Simplest Way to Create a New Application Credential[](#step-2-the-simplest-way-to-create-a-new-application-credential "Permalink to this headline")
Step 2 The Simplest Way to Create a New Application Credential[🔗](#step-2-the-simplest-way-to-create-a-new-application-credential "Permalink to this headline")
---------------------------------------------------------------------------------------------------------------------------------------------------------------
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**:
@ -89,7 +89,7 @@ The new application credential will be both formed and shown on the screen:
![create_new_with_name.png](../_images/create_new_with_name.png)
Step 3 Using All Parameters to Create a New Application Credential[](#step-3-using-all-parameters-to-create-a-new-application-credential "Permalink to this headline")
Step 3 Using All Parameters to Create a New Application Credential[🔗](#step-3-using-all-parameters-to-create-a-new-application-credential "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Here is the meaning of related parameters:
@ -144,7 +144,7 @@ The result is:
The name of the new application credential will be **foo-dev-member4**, will be used by role **\_member\_** and so on. The part of the command starting with **| jq -r** prints only the values of credentials **id** and **secret** as you have to enter those value into the *clouds.yml* file in order to activate the recognition part of the process.
Step 4 Enter id and secret into clouds.yml[](#step-4-enter-id-and-secret-into-clouds-yml "Permalink to this headline")
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.
@ -227,7 +227,7 @@ This is how it should look in the editor:
Save it with **Ctrl**-**X**, then press **Y** and Enter.
Step 5 Gain access to the cloud by specifying OS\_CLOUD or --os-cloud[](#step-5-gain-access-to-the-cloud-by-specifying-os-cloud-or-os-cloud "Permalink to this headline")
Step 5 Gain access to the cloud by specifying OS\_CLOUD or --os-cloud[🔗](#step-5-gain-access-to-the-cloud-by-specifying-os-cloud-or-os-cloud "Permalink to this headline")
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Application credentials give access to all of the activated regions and you have to specify which one to use. Specify it as a value of parameter **--os-region**, for instance, WAW3-2, WAW4-1 (or what else have you).
@ -268,7 +268,7 @@ If you had two or more clouds defined in the *clouds.yml* file, then using **--o
In both cases, you can access the cloud without specifying the password, which was the goal in the first place.
Environment variable-based storage[](#environment-variable-based-storage "Permalink to this headline")
Environment variable-based storage[🔗](#environment-variable-based-storage "Permalink to this headline")
-------------------------------------------------------------------------------------------------------
You can export them as environment variables. This increases security, especially in virtual machines. Also, automation tools can use them dynamically.
@ -294,7 +294,7 @@ source ~/.bashrc
This method is useful for scripted deployments, temporary sessions, and when you don’t want credentials stored in files.
What To Do Next[](#what-to-do-next "Permalink to this headline")
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
-----------------------------------------------------------------
Here are some articles that use application credentials:

2
docs/cloud/How-to-install-Python-virtualenv-or-virtualenvwrapper-on-CloudFerro-Cloud.html.md
View File

@ -1,4 +1,4 @@
How to install Python virtualenv or virtualenvwrapper on CloudFerro Cloud[](#how-to-install-python-virtualenv-or-virtualenvwrapper-on-brand-name "Permalink to this headline")
How to install Python virtualenv or virtualenvwrapper on CloudFerro Cloud[🔗](#how-to-install-python-virtualenv-or-virtualenvwrapper-on-brand-name "Permalink to this headline")
===============================================================================================================================================================================
Virtualenv is a tool with which you are able to create isolated Python environments. It is mainly used to get rid of problems with dependencies and versions.

6
docs/cloud/How-to-start-a-VM-from-a-snapshot-on-CloudFerro-Cloud.html.md
View File

@ -1,7 +1,7 @@
How to start a VM from a snapshot on CloudFerro Cloud[](#how-to-start-a-vm-from-a-snapshot-on-brand-name "Permalink to this headline")
How to start a VM from a snapshot on CloudFerro Cloud[🔗](#how-to-start-a-vm-from-a-snapshot-on-brand-name "Permalink to this headline")
=======================================================================================================================================
a) Volume Snapshot[](#a-volume-snapshot "Permalink to this headline")
a) Volume Snapshot[🔗](#a-volume-snapshot "Permalink to this headline")
----------------------------------------------------------------------
1. Choose the desired virtual machine (booted from Volume) and click on the “Create snapshot” button.
@ -38,7 +38,7 @@ a) Volume Snapshot[](#a-volume-snapshot "Permalink to this headline")
![snap8.png](../_images/snap8.png)
b) Image Snapshot[](#b-image-snapshot "Permalink to this headline")
b) Image Snapshot[🔗](#b-image-snapshot "Permalink to this headline")
--------------------------------------------------------------------
1.Choose the desired virtual machine (booted from Glance image) and click on the “Create snapshot” button.

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

@ -1,9 +1,9 @@
How to start a VM from instance snapshot using Horizon dashboard on CloudFerro Cloud[](#how-to-start-a-vm-from-instance-snapshot-using-horizon-dashboard-on-brand-name "Permalink to this headline")
How to start a VM from instance snapshot using Horizon dashboard on CloudFerro Cloud[🔗](#how-to-start-a-vm-from-instance-snapshot-using-horizon-dashboard-on-brand-name "Permalink to this headline")
=====================================================================================================================================================================================================
In this article, you will learn how to create a virtual machine from an instance snapshot using Horizon dashboard.
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**

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

@ -1,4 +1,4 @@
How to transfer volumes between domains and projects using Horizon dashboard on CloudFerro Cloud[](#how-to-transfer-volumes-between-domains-and-projects-using-horizon-dashboard-on-brand-name "Permalink to this headline")
How to transfer volumes between domains and projects using Horizon dashboard on CloudFerro 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.
@ -9,14 +9,14 @@ This article covers changing the assignment of a volume to a project. This allow
The *source* project and *destination* project must both be on the same cloud (for example WAW3-2). They can (but don’t have to) belong to different users from different domains and organizations.
What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this headline")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * Initializing transfer of volume
> * Accepting transfer of volume
> * Cancelling transfer of volume
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**
@ -47,7 +47,7 @@ To access each of these projects directly (if possible), depending on the circum
If you don’t have direct access to any of these projects, you probably can request their members to execute commands mentioned in this article.
Step 1: Initializing transfer of volume[](#step-1-initializing-transfer-of-volume "Permalink to this headline")
Step 1: Initializing transfer of volume[🔗](#step-1-initializing-transfer-of-volume "Permalink to this headline")
----------------------------------------------------------------------------------------------------------------
Perform this step in the *source* project.
@ -86,7 +86,7 @@ Your volume should now have the following **Status**: **Awaiting Transfer**.
Note that after initializing the transfer, the volume cannot be connected to any virtual machine until the transfer is accepted or cancelled. To learn how to cancel the transfer (if you, say, accidentally chose the wrong volume), see section **Cancelling transfer of volume** near the end of the article.
Step 2: Accepting transfer of volume[](#step-2-accepting-transfer-of-volume "Permalink to this headline")
Step 2: Accepting transfer of volume[🔗](#step-2-accepting-transfer-of-volume "Permalink to this headline")
----------------------------------------------------------------------------------------------------------
Perform this step in the *source* project.
@ -107,7 +107,7 @@ The volume should now be visible on the list:
![transfer-volume-between-projects-horizon-21_creodias.png](../_images/transfer-volume-between-projects-horizon-21_creodias.png)
Cancelling transfer of volume[](#cancelling-transfer-of-volume "Permalink to this headline")
Cancelling transfer of volume[🔗](#cancelling-transfer-of-volume "Permalink to this headline")
---------------------------------------------------------------------------------------------
If you, say, accidentally initiated transfer for a wrong volume and nobody accepts that transfer, it can be cancelled.
@ -138,7 +138,7 @@ After cancelling, your volume should now once again have status **Available**:
![transfer-volume-between-projects-horizon-11_creodias.png](../_images/transfer-volume-between-projects-horizon-11_creodias.png)
What To Do Next[](#what-to-do-next "Permalink to this headline")
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 CloudFerro Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-OpenStack-Horizon-on-CloudFerro-Cloud.html.md)

6
docs/cloud/How-to-upload-custom-image-to-CloudFerro-Cloud-cloud-using-OpenStack-Horizon-dashboard.html.md
View File

@ -1,9 +1,9 @@
How to upload custom image to CloudFerro 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 CloudFerro Cloud cloud using OpenStack Horizon dashboard[🔗](#how-to-upload-custom-image-to-brand-name-cloud-using-openstack-horizon-dashboard "Permalink to this headline")
=========================================================================================================================================================================================================
In this tutorial, you will upload custom image stored on your local computer to CloudFerro Cloud cloud, using the Horizon Dashboard. The uploaded image will be available within your project alongside default images from CloudFerro 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")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * How to check for the presence of image in CloudFerro Cloud cloud
@ -12,7 +12,7 @@ What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this h
> * Example: how to upload image for Debian 11
> * What happens if you lose Internet connection during upload
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**

6
docs/cloud/How-to-upload-your-custom-image-using-OpenStack-CLI-on-CloudFerro-Cloud.html.md
View File

@ -1,9 +1,9 @@
How to upload your custom image using OpenStack CLI on CloudFerro Cloud[](#how-to-upload-your-custom-image-using-openstack-cli-on-brand-name "Permalink to this headline")
How to upload your custom image using OpenStack CLI on CloudFerro Cloud[🔗](#how-to-upload-your-custom-image-using-openstack-cli-on-brand-name "Permalink to this headline")
===========================================================================================================================================================================
In this tutorial, you will upload custom image stored on your local computer to CloudFerro Cloud cloud, using the OpenStack CLI client. The uploaded image will be available within your project alongside default images from CloudFerro 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")
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
@ -12,7 +12,7 @@ What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this h
> * Example: how to upload image for Debian 11
> * What happens if you lose Internet connection during upload
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**

2
docs/cloud/How-to-use-Docker-on-CloudFerro-Cloud.html.md
View File

@ -1,4 +1,4 @@
How to install and use Docker on Ubuntu 24.04[](#how-to-install-and-use-docker-on-ubuntu-24-04 "Permalink to this headline")
How to install and use Docker on Ubuntu 24.04[🔗](#how-to-install-and-use-docker-on-ubuntu-24-04 "Permalink to this headline")
=============================================================================================================================
This guide will walk you through

24
docs/cloud/How-to-use-GUI-in-Linux-VM-on-CloudFerro-Cloud-and-access-it-from-local-Linux-computer.html.md
View File

@ -1,4 +1,4 @@
How to Use GUI in Linux VM on CloudFerro Cloud and access it From Local Linux Computer[](#how-to-use-gui-in-linux-vm-on-brand-name-and-access-it-from-local-linux-computer "Permalink to this headline")
How to Use GUI in Linux VM on CloudFerro Cloud and access it From Local Linux Computer[🔗](#how-to-use-gui-in-linux-vm-on-brand-name-and-access-it-from-local-linux-computer "Permalink to this headline")
=========================================================================================================================================================================================================
In this article you will learn how to use GUI (graphical user interface) on a Linux virtual machine running on CloudFerro Cloud cloud.
@ -7,7 +7,7 @@ For this purpose, you will install and use **X2Go** on your local Linux computer
This article covers the installation of two desktop environments: MATE and XFCE. Choose the one that suits you best.
What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this headline")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * Installing X2Go client
@ -15,7 +15,7 @@ What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this h
> * Connecting to your virtual machine using X2Go client
> * Basic troubleshooting
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**
@ -34,7 +34,7 @@ You need a Linux virtual machine running on CloudFerro Cloud cloud. You need to
This article was written for virtual machines using a default Ubuntu 20.04 image on cloud. Adjust the instructions from this article accordingly if your virtual machine has a different Linux distribution.
Step 1: Install X2Go client[](#step-1-install-x2go-client "Permalink to this headline")
Step 1: Install X2Go client[🔗](#step-1-install-x2go-client "Permalink to this headline")
----------------------------------------------------------------------------------------
Open the terminal on your local Linux computer and update your packages by executing the following command:
@ -51,10 +51,10 @@ sudo apt install x2goclient
```
Step 2: Install the desktop environment on your VM[](#step-2-install-the-desktop-environment-on-your-vm "Permalink to this headline")
Step 2: Install the desktop environment on your VM[🔗](#step-2-install-the-desktop-environment-on-your-vm "Permalink to this headline")
--------------------------------------------------------------------------------------------------------------------------------------
### Method 1: Installing MATE[](#method-1-installing-mate "Permalink to this headline")
### Method 1: Installing MATE[🔗](#method-1-installing-mate "Permalink to this headline")
Connect to your VM using SSH. Update your packages there:
@ -81,7 +81,7 @@ sudo reboot
```
### Method 2: Installing XFCE[](#method-2-installing-xfce "Permalink to this headline")
### Method 2: Installing XFCE[🔗](#method-2-installing-xfce "Permalink to this headline")
Connect to your VM using SSH. Update your packages there:
@ -108,7 +108,7 @@ sudo reboot
```
Step 3: Connect to your VM using X2Go[](#step-3-connect-to-your-vm-using-x2go "Permalink to this headline")
Step 3: Connect to your VM using X2Go[🔗](#step-3-connect-to-your-vm-using-x2go "Permalink to this headline")
------------------------------------------------------------------------------------------------------------
Open X2Go on your local Linux computer. If you haven’t configured any session yet, you should get the window used for creating one:
@ -145,7 +145,7 @@ If you, however, chose XFCE, it should look like this:
![linux-gui-06_creodias.png](../_images/linux-gui-06_creodias.png)
Troubleshooting - Using the terminal emulator on XFCE[](#troubleshooting-using-the-terminal-emulator-on-xfce "Permalink to this headline")
Troubleshooting - Using the terminal emulator on XFCE[🔗](#troubleshooting-using-the-terminal-emulator-on-xfce "Permalink to this headline")
-------------------------------------------------------------------------------------------------------------------------------------------
If the button **Terminal Emulator** on your taskbar does not launch your terminal, click the **Applications** menu in the upper left corner of the screen:
@ -170,12 +170,12 @@ Click **Close**.
The button should now launch the terminal emulator correctly.
Troubleshooting - Keyboard layout[](#troubleshooting-keyboard-layout "Permalink to this headline")
Troubleshooting - Keyboard layout[🔗](#troubleshooting-keyboard-layout "Permalink to this headline")
---------------------------------------------------------------------------------------------------
If you discover that the system does not use the keyboard layout you chose during the installation of the desktop environment, you will need to set it manually. The process differs depending on the desktop environment you chose.
### MATE[](#mate "Permalink to this headline")
### MATE[🔗](#mate "Permalink to this headline")
Click the **Menu** in the upper left corner of the screen:
@ -195,7 +195,7 @@ Navigate to the **Layouts** tab:
Here, you can add or remove keyboard layouts depending on your needs.
### XFCE[](#xfce "Permalink to this headline")
### XFCE[🔗](#xfce "Permalink to this headline")
From the **Applications** menu in the upper left corner of the screen choose **Settings** -> **Keyboard**. You should get the following window:

14
docs/cloud/How-to-use-Security-Groups-in-Horizon-on-CloudFerro-Cloud.html.md
View File

@ -1,11 +1,11 @@
How to use Security Groups in Horizon on CloudFerro Cloud[](#how-to-use-security-groups-in-horizon-on-brand-name "Permalink to this headline")
How to use Security Groups in Horizon on CloudFerro 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.
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.
Viewing the security groups[](#viewing-the-security-groups "Permalink to this headline")
Viewing the security groups[🔗](#viewing-the-security-groups "Permalink to this headline")
-----------------------------------------------------------------------------------------
To check your current security groups, please follow these steps:
@ -21,7 +21,7 @@ You will see the list of your security groups there. The following groups should
![use-security-groups-1_creodias.png](../_images/use-security-groups-1_creodias.png)
Creating a new security group[](#creating-a-new-security-group "Permalink to this headline")
Creating a new security group[🔗](#creating-a-new-security-group "Permalink to this headline")
---------------------------------------------------------------------------------------------
In order to create a new security group, please follow these steps:
@ -46,7 +46,7 @@ If you want to access that screen later, you can click the **Manage Rules** butt
By default, your new security group should contain two rules seen on the screenshot above - the first one allows all outgoing traffic on IPv4 and the second one allows all outgoing traffic on IPv6.
Adding security rules to a security group[](#adding-security-rules-to-a-security-group "Permalink to this headline")
Adding security rules to a security group[🔗](#adding-security-rules-to-a-security-group "Permalink to this headline")
---------------------------------------------------------------------------------------------------------------------
In the **Manage Security Rules** screen that you entered in the previous step, click the **Add Rule** button.
@ -96,12 +96,12 @@ These options apply to all ports of ICMP, TCP and UPD, respectively.
The drop-down list **Rule** also contains templates for commonly used services like DNS (Domain Name Services), HTTP (Hypertext Transfer Protocol) or SMTP (Simple Mail Transfer Protocol). If you choose one of them, you only have to provide the information about the **Remote** - **CIDR** or **Security Group**. The explanation for those options is in the **Custom TCP Rule** section.
Adding a Security Group to your VM[](#adding-a-security-group-to-your-vm "Permalink to this headline")
Adding a Security Group to your VM[🔗](#adding-a-security-group-to-your-vm "Permalink to this headline")
-------------------------------------------------------------------------------------------------------
You can apply your security group to your VM either during or after creating it.
### During its creation[](#during-its-creation "Permalink to this headline")
### During its creation[🔗](#during-its-creation "Permalink to this headline")
During the process of creating your virtual machine you can add security groups to it. This happens during the **Security Groups** step:
@ -111,7 +111,7 @@ You can add security groups to your VM by using the **↑** button an remove the
![use-security-groups-6_creodias.png](../_images/use-security-groups-6_creodias.png)
### After its creation[](#after-its-creation "Permalink to this headline")
### After its creation[🔗](#after-its-creation "Permalink to this headline")
Go to **Compute** > **Instances**. Click the drop-down menu in the row containing information about the to which you wish to apply your rule (column **Actions**). Select **Edit Security Groups**. You should see the window similar to this:

28
docs/cloud/OpenStack-user-roles-on-CloudFerro-Cloud.html.md
View File

@ -1,11 +1,11 @@
OpenStack User Roles on CloudFerro Cloud[](#openstack-user-roles-on-brand-name "Permalink to this headline")
OpenStack User Roles on CloudFerro Cloud[🔗](#openstack-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.
This guide simplifies OpenStack roles for casual users of CloudFerro 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")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * Frequently used user roles
@ -23,7 +23,7 @@ What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this h
>
> * Dictionary of other roles
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
**1. Account**
@ -51,10 +51,10 @@ Ensure you know the following OpenStack commands:
[How To Access Kubernetes Cluster Post Deployment Using Kubectl On CloudFerro Cloud OpenStack Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-CloudFerro-Cloud-OpenStack-Magnum.html.md)
Frequently used user roles[](#frequently-used-user-roles "Permalink to this headline")
Frequently used user roles[🔗](#frequently-used-user-roles "Permalink to this headline")
---------------------------------------------------------------------------------------
### Common user roles[](#common-user-roles "Permalink to this headline")
### Common user roles[🔗](#common-user-roles "Permalink to this headline")
**member**
: Grants standard access to project resources.
@ -78,7 +78,7 @@ Frequently used user roles[](#frequently-used-user-roles "Permalink to this h
* Horizon: **Project** -> **Overview**
* CLI: **openstack server list**, **openstack project list**
### Roles for Kubernetes users[](#roles-for-kubernetes-users "Permalink to this headline")
### Roles for Kubernetes users[🔗](#roles-for-kubernetes-users "Permalink to this headline")
**k8s\_admin**
: Administrative access to manage Kubernetes clusters and resources.
@ -98,7 +98,7 @@ Frequently used user roles[](#frequently-used-user-roles "Permalink to this h
* Horizon: **Kubernetes** -> **Overview**
* CLI: **kubectl get pods**, **kubectl describe pod**
### Roles for Load Balancer users[](#roles-for-load-balancer-users "Permalink to this headline")
### Roles for Load Balancer users[🔗](#roles-for-load-balancer-users "Permalink to this headline")
**load-balancer\_member**
: Grants access to deploy applications behind load balancers.
@ -112,7 +112,7 @@ Frequently used user roles[](#frequently-used-user-roles "Permalink to this h
* Horizon: **Network** -> **Load Balancers**
* CLI: **openstack loadbalancer show**, **openstack loadbalancer stats show**
How to View Roles in Horizon[](#how-to-view-roles-in-horizon "Permalink to this headline")
How to View Roles in Horizon[🔗](#how-to-view-roles-in-horizon "Permalink to this headline")
-------------------------------------------------------------------------------------------
You can view roles in Horizon by navigating to **Identity** -> **Roles**.
@ -125,12 +125,12 @@ Assigning multiple roles is best done during project creation rather than user c
![openstack-user-roles-create-4.png](../_images/openstack-user-roles-create-4.png)
Examples of using user roles[](#examples-of-using-user-roles "Permalink to this headline")
Examples of using user roles[🔗](#examples-of-using-user-roles "Permalink to this headline")
-------------------------------------------------------------------------------------------
The following articles, as one of many steps, describe how to assign a role to the new project, credential, user or group.
### Using user roles while creating application credential in Horizon[](#using-user-roles-while-creating-application-credential-in-horizon "Permalink to this headline")
### 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.
@ -140,7 +140,7 @@ That S3 article selects user roles when creating an application credential, thro
![user-roles-list-create-2.png](../_images/user-roles-list-create-2.png)
### Using user roles while creating application credential via the CLI[](#using-user-roles-while-creating-application-credential-via-the-cli "Permalink to this headline")
### Using user roles while creating application credential via the CLI[🔗](#using-user-roles-while-creating-application-credential-via-the-cli "Permalink to this headline")
This is the main article about application credentials; it is mostly using CLI:
@ -150,7 +150,7 @@ Here is how to specify user roles through CLI parameters:
![user-roles-list-create-1.png](../_images/user-roles-list-create-1.png)
### Using user roles while creating a new project[](#using-user-roles-while-creating-a-new-project "Permalink to this headline")
### 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 CloudFerro Cloud Cloud](../openstackcli/How-To-Create-and-Configure-New-Project-on-CloudFerro-Cloud-Cloud.html.md) we use command **Project Members** to define which users to include into the project:
@ -167,7 +167,7 @@ You would then continue by defining the roles for each user in the project:
![user-roles-list-create-6.png](../_images/user-roles-list-create-6.png)
### Using member role only while creating a new user[](#using-member-role-only-while-creating-a-new-user "Permalink to this headline")
### 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**.
@ -177,7 +177,7 @@ In SLURM article, we first create a new OpenStack Keystone user, with the role o
That user can login to Horizon and use project resources together with other users which are defined in a similar way.
Dictionary of other roles[](#dictionary-of-other-roles "Permalink to this headline")
Dictionary of other roles[🔗](#dictionary-of-other-roles "Permalink to this headline")
-------------------------------------------------------------------------------------
**admin**

18
docs/cloud/Resizing-a-virtual-machine-using-OpenStack-Horizon-on-CloudFerro-Cloud.html.md
View File

@ -1,7 +1,7 @@
Resizing a virtual machine using OpenStack Horizon on CloudFerro Cloud[](#resizing-a-virtual-machine-using-openstack-horizon-on-brand-name "Permalink to this headline")
Resizing a virtual machine using OpenStack Horizon on CloudFerro Cloud[🔗](#resizing-a-virtual-machine-using-openstack-horizon-on-brand-name "Permalink to this headline")
=========================================================================================================================================================================
Introduction[](#introduction "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.
@ -16,7 +16,7 @@ After the instance is spawned, it is possible to change one flavor for another,
In this article, we are going to resize VMs using commands in OpenStack Horizon.
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**
@ -41,7 +41,7 @@ Also:
> * A flavor with the desired resource configuration exists.
> * Adequate resources are available in your OpenStack environment to accommodate the resize.
Creating a new VM[](#creating-a-new-vm "Permalink to this headline")
Creating a new VM[🔗](#creating-a-new-vm "Permalink to this headline")
---------------------------------------------------------------------
To illustrate the commands in this article, let us create a new VM in order to start with a clean slate. (It goes without saying that you can practice with any of the already existing VMs in your account.)
@ -60,7 +60,7 @@ Finish the process of creating a new VM and let it spawn:
Let us now resize the VM called **Resizing**.
Steps to Resize the VM[](#steps-to-resize-the-vm "Permalink to this headline")
Steps to Resize the VM[🔗](#steps-to-resize-the-vm "Permalink to this headline")
-------------------------------------------------------------------------------
Locate the VM by using Horizon commands **Compute** -> **Instances**.
@ -84,7 +84,7 @@ So, select **eo2.xlarge** as the new flavor. This screen shows its parameters:
![fwaas-openvpn-v2-34.png](../_images/fwaas-openvpn-v2-34.png)
Advanced Options[](#advanced-options "Permalink to this headline")
Advanced Options[🔗](#advanced-options "Permalink to this headline")
-------------------------------------------------------------------
**Advanced Options** tab contains two further options for resizing the instance.
@ -102,7 +102,7 @@ Server Group
![resize-vm-horizon-11.png](../_images/resize-vm-horizon-11.png)
Resize the VM[](#resize-the-vm "Permalink to this headline")
Resize the VM[🔗](#resize-the-vm "Permalink to this headline")
-------------------------------------------------------------
Anyways, click on **Resize** to proceed with the resizing of the VM.
@ -117,7 +117,7 @@ If you encounter issues, you can choose **Revert Resize** to return the VM to it
Or, if the resizing is finished, you can again use option **Resize instance** and choose the flavor from which you started (**eo2a.large** in this case). This process of scaling down is much faster than the process of scaling up.
Troubleshooting[](#troubleshooting "Permalink to this headline")
Troubleshooting[🔗](#troubleshooting "Permalink to this headline")
-----------------------------------------------------------------
If any of the flavor parameters does not match up, the resizing will fail.
@ -128,7 +128,7 @@ You will then see balloon help in the right upper corner:
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")
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 CloudFerro Cloud](../openstackcli/Resizing-a-virtual-machine-using-OpenStack-CLI-on-CloudFerro-Cloud.html.md)

6
docs/cloud/Spot-instances-on-CloudFerro-Cloud.html.md
View File

@ -1,16 +1,16 @@
Spot instances on CloudFerro Cloud[](#spot-instances-on-brand-name "Permalink to this headline")
Spot instances on CloudFerro Cloud[🔗](#spot-instances-on-brand-name "Permalink to this headline")
=================================================================================================
Spot instance is resource similar to Amazon EC2 Spot Instances or Google Spot VMs. In short, user is provided with unused computational resources for a discounted price but those resources can be terminated on a short time notice whenever on-demand usage increases. The main use case are ephemeral workflows which can deal with being terminated unexpectedly and/or orchestration platforms which can deal with forced scaling down of available resources e.g. Kubernetes clusters.
What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this headline")
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------
> * How to create spot instances
> * Additional configuration via tags
> * What is the expected behaviour
Prerequisites[](#prerequisites "Permalink to this headline")
Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------
No. 1 **Account**

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

@ -1,4 +1,4 @@
Status Power State and dependencies in billing of instance VMs on CloudFerro Cloud[](#status-power-state-and-dependencies-in-billing-of-instance-vms-on-brand-name "Permalink to this headline")
Status Power State and dependencies in billing of instance VMs on CloudFerro 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:
@ -10,7 +10,7 @@ In OpenStack, instances have their own Status and Power State:
There are six Power states, divided into two groups, depending on whether the VM is running or not.
Power state while VM is running[](#power-state-while-vm-is-running "Permalink to this headline")
Power state while VM is running[🔗](#power-state-while-vm-is-running "Permalink to this headline")
-------------------------------------------------------------------------------------------------
**NO STATE**
@ -22,7 +22,7 @@ Power state while VM is running[](#power-state-while-vm-is-running "Permalink
**PAUSED**
: VM is frozen and a memory dump is made.
Power state while VM is turned off[](#power-state-while-vm-is-turned-off "Permalink to this headline")
Power state while VM is turned off[🔗](#power-state-while-vm-is-turned-off "Permalink to this headline")
-------------------------------------------------------------------------------------------------------
**SHUT DOWN**
@ -34,7 +34,7 @@ Power state while VM is turned off[](#power-state-while-vm-is-turned-off "Per
**SUSPENDED**
: VM is blocked by system (most likely because of negative credit on account).
Status and its conditions[](#status-and-its-conditions "Permalink to this headline")
Status and its conditions[🔗](#status-and-its-conditions "Permalink to this headline")
-------------------------------------------------------------------------------------
Status may have one of the following conditions:

2
docs/cloud/VM-created-with-option-Create-New-Volume-No-on-CloudFerro-Cloud.html.md
View File

@ -1,4 +1,4 @@
VM created with option Create New Volume No on CloudFerro Cloud[](#vm-created-with-option-create-new-volume-no-on-brand-name "Permalink to this headline")
VM created with option Create New Volume No on CloudFerro Cloud[🔗](#vm-created-with-option-create-new-volume-no-on-brand-name "Permalink to this headline")
===========================================================================================================================================================
During creation of a VM you can select a source. If you choose “Image”, you can then choose **Yes** or **No** for the option “**Create New Volume**”.

2
docs/cloud/VM-created-with-option-Create-New-Volume-Yes-on-CloudFerro-Cloud.html.md
View File

@ -1,4 +1,4 @@
VM created with option Create New Volume Yes on CloudFerro Cloud[](#vm-created-with-option-create-new-volume-yes-on-brand-name "Permalink to this headline")
VM created with option Create New Volume Yes on CloudFerro Cloud[🔗](#vm-created-with-option-create-new-volume-yes-on-brand-name "Permalink to this headline")
=============================================================================================================================================================
Note

2
docs/cloud/What-Image-Formats-are-available-in-OpenStack-CloudFerro-Cloud-Cloud.html.md
View File

@ -1,4 +1,4 @@
What Image Formats are Available in OpenStack CloudFerro Cloud cloud[](#what-image-formats-are-available-in-openstack-brand-name-cloud "Permalink to this headline")
What Image Formats are Available in OpenStack CloudFerro Cloud cloud[🔗](#what-image-formats-are-available-in-openstack-brand-name-cloud "Permalink to this headline")
=====================================================================================================================================================================
In CloudFerro Cloud OpenStack ten image format extensions are available:

2
docs/cloud/What-is-an-OpenStack-domain-on-CloudFerro-Cloud.html.md
View File

@ -1,4 +1,4 @@
What is an OpenStack domain on CloudFerro Cloud[](#what-is-an-openstack-domain-on-brand-name "Permalink to this headline")
What is an OpenStack domain on CloudFerro Cloud[🔗](#what-is-an-openstack-domain-on-brand-name "Permalink to this headline")
===========================================================================================================================
**Domain**

2
docs/cloud/What-is-an-OpenStack-project-on-CloudFerro-Cloud.html.md
View File

@ -1,4 +1,4 @@
What is an OpenStack project on CloudFerro Cloud[](#what-is-an-openstack-project-on-brand-name "Permalink to this headline")
What is an OpenStack project on CloudFerro Cloud[🔗](#what-is-an-openstack-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).

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

@ -6,7 +6,7 @@
* [DNS as a Service on CloudFerro Cloud Hosting](DNS-as-a-Service-on-CloudFerro-Cloud-Hosting.html.md)
* [Dashboard Overview Project Quotas And Flavors Limits on CloudFerro Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-CloudFerro-Cloud.html.md)
* [How To Create a New Linux VM With NVIDIA Virtual GPU in the OpenStack Dashboard Horizon on CloudFerro Cloud](How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-OpenStack-Dashboard-Horizon-on-CloudFerro-Cloud.html.md)
* [Performing administrative tasks within Windows based VMs[](#performing-administrative-tasks-within-windows-based-vms "Permalink to this headline")](How-to-access-the-VM-from-OpenStack-console-on-CloudFerro-Cloud.html.md)
* [Performing administrative tasks within Windows based VMs[🔗](#performing-administrative-tasks-within-windows-based-vms "Permalink to this headline")](How-to-access-the-VM-from-OpenStack-console-on-CloudFerro-Cloud.html.md)
* [How to clone existing and configured VMs on CloudFerro Cloud](How-to-clone-existing-and-configured-VMs-on-CloudFerro-Cloud.html.md)
* [How to create Windows VM on OpenStack Horizon and access it via web console on CloudFerro Cloud](How-to-create-Windows-VM-on-OpenStack-Horizon-and-access-it-via-web-console-on-CloudFerro-Cloud.html.md)
* [How to create a Linux VM and access it from Linux command line on CloudFerro Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-CloudFerro-Cloud.html.md)
@ -25,9 +25,9 @@
* [How to upload custom image to CloudFerro Cloud cloud using OpenStack Horizon dashboard](How-to-upload-custom-image-to-CloudFerro-Cloud-cloud-using-OpenStack-Horizon-dashboard.html.md)
* [How to upload your custom image using OpenStack CLI on CloudFerro Cloud](How-to-upload-your-custom-image-using-OpenStack-CLI-on-CloudFerro-Cloud.html.md)
* [How to use Docker on CloudFerro Cloud](How-to-use-Docker-on-CloudFerro-Cloud.html.md)
* [Method 1: Installing MATE[](#method-1-installing-mate "Permalink to this headline")](How-to-use-GUI-in-Linux-VM-on-CloudFerro-Cloud-and-access-it-from-local-Linux-computer.html.md)
* [During its creation[](#during-its-creation "Permalink to this headline")](How-to-use-Security-Groups-in-Horizon-on-CloudFerro-Cloud.html.md)
* [Common user roles[](#common-user-roles "Permalink to this headline")](OpenStack-user-roles-on-CloudFerro-Cloud.html.md)
* [Method 1: Installing MATE[🔗](#method-1-installing-mate "Permalink to this headline")](How-to-use-GUI-in-Linux-VM-on-CloudFerro-Cloud-and-access-it-from-local-Linux-computer.html.md)
* [During its creation[🔗](#during-its-creation "Permalink to this headline")](How-to-use-Security-Groups-in-Horizon-on-CloudFerro-Cloud.html.md)
* [Common user roles[🔗](#common-user-roles "Permalink to this headline")](OpenStack-user-roles-on-CloudFerro-Cloud.html.md)
* [Resizing a virtual machine using OpenStack Horizon on CloudFerro Cloud](Resizing-a-virtual-machine-using-OpenStack-Horizon-on-CloudFerro-Cloud.html.md)
* [Spot instances on CloudFerro Cloud](Spot-instances-on-CloudFerro-Cloud.html.md)
* [Status Power State and dependences in billing of instances VMs on CloudFerro Cloud](Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-CloudFerro-Cloud.html.md)