link icon replaced
This commit is contained in:
@ -1,7 +1,7 @@
|
||||
How to Create and Configure New Openstack Project Through Horizon on CloudFerro Cloud Cloud[](#how-to-create-and-configure-new-openstack-project-through-horizon-on-brand-name-cloud-name-cloud "Permalink to this headline")
|
||||
How to Create and Configure New Openstack Project Through Horizon on CloudFerro Cloud Cloud[🔗](#how-to-create-and-configure-new-openstack-project-through-horizon-on-brand-name-cloud-name-cloud "Permalink to this headline")
|
||||
==============================================================================================================================================================================================================================
|
||||
|
||||
Default elements of the account[](#default-elements-of-the-account "Permalink to this headline")
|
||||
Default elements of the account[🔗](#default-elements-of-the-account "Permalink to this headline")
|
||||
-------------------------------------------------------------------------------------------------
|
||||
|
||||
When you first create your account at CloudFerro Cloud hosting, default values for the account will be applied. Among others, you will
|
||||
@ -25,7 +25,7 @@ In other words, the users of the account won’t have access to the Internet.
|
||||
|
||||
In this article you will see how to overcome these problems.
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Hosting**
|
||||
@ -46,7 +46,7 @@ Here is how to create a network with router:
|
||||
|
||||
[How to create a network with router in Horizon Dashboard on CloudFerro Cloud](../networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-CloudFerro-Cloud.html.md)
|
||||
|
||||
Default values in the tenant manager account[](#default-values-in-the-tenant-manager-account "Permalink to this headline")
|
||||
Default values in the tenant manager account[🔗](#default-values-in-the-tenant-manager-account "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Click on **Network** -> **Networks** and verify the presence of the three default networks. Since the cloud contains number **341** in its name, the networks will have it too: **cloud\_00341\_3** and **eodata\_00341\_**.
|
||||
@ -74,12 +74,12 @@ The default security groups are:
|
||||
|
||||
The former shuts down any communication to the virtual machine for security reasons while the latter opens up only the ports for normal use. In this case, it will be for traffic of types **ping**, **ssh**, **icmp** and **rdp**. Please see Prerequisite No. 3 for definition of those terms.
|
||||
|
||||
Create a New Project[](#create-a-new-project "Permalink to this headline")
|
||||
Create a New Project[🔗](#create-a-new-project "Permalink to this headline")
|
||||
---------------------------------------------------------------------------
|
||||
|
||||
A project can contain users, groups and their roles so the first step is to define a project and later add users, groups and roles.
|
||||
|
||||
Step 1 Create Project[](#step-1-create-project "Permalink to this headline")
|
||||
Step 1 Create Project[🔗](#step-1-create-project "Permalink to this headline")
|
||||
-----------------------------------------------------------------------------
|
||||
|
||||
Choose **Identity** → **Projects** menu on the left side of the screen.
|
||||
@ -127,7 +127,7 @@ As mentioned earlier, your new project will **not** have access to the external
|
||||
|
||||
For security groups, the situation is similar: the default one is present, but the **allow\_ping\_ssh\_icmp\_rdp** security group is missing.
|
||||
|
||||
Step 2 Add external network to the project[](#step-2-add-external-network-to-the-project "Permalink to this headline")
|
||||
Step 2 Add external network to the project[🔗](#step-2-add-external-network-to-the-project "Permalink to this headline")
|
||||
-----------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
To add external network to such project you must contact Customer Support by creating a ticket. Instructions how to do that are in article [Helpdesk and Support](../accountmanagement/Help-Desk-And-Support.html.md). The ticket should include project ID from the Projects list. To get the project ID, click on **Project** -> **API Access**
|
||||
@ -142,7 +142,7 @@ Copy those values and put them into the email message in Helpdesk window. Click
|
||||
|
||||

|
||||
|
||||
Step 3 Add security group to the project[](#step-3-add-security-group-to-the-project "Permalink to this headline")
|
||||
Step 3 Add security group to the project[🔗](#step-3-add-security-group-to-the-project "Permalink to this headline")
|
||||
-------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
When the support answers, you will see **external** network in the network list. Then create security group and enable ports **22** (SSH) and **3389** (RDP) following the instructions in Prerequisite No. 3. Your security group should look like this:
|
||||
@ -151,12 +151,12 @@ When the support answers, you will see **external** network in the network list.
|
||||
|
||||
Port 22 will enable SSH access to the instance, while port 3389 will enable access through RDP. SSH and RDP are protocols for accessing a virtual machine from local Linux or Windows machines, respectively.
|
||||
|
||||
Step 4 Create network with router[](#step-4-create-network-with-router "Permalink to this headline")
|
||||
Step 4 Create network with router[🔗](#step-4-create-network-with-router "Permalink to this headline")
|
||||
-----------------------------------------------------------------------------------------------------
|
||||
|
||||
The last step is to create a network with a router. See Prerequisite No. 4.
|
||||
|
||||
What To Do Next[](#what-to-do-next "Permalink to this headline")
|
||||
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
|
||||
-----------------------------------------------------------------
|
||||
|
||||
Your **testproject** is ready for creating new instances. For example, see articles:
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
How to access object storage using OpenStack CLI on CloudFerro Cloud[](#how-to-access-object-storage-using-openstack-cli-on-brand-name "Permalink to this headline")
|
||||
How to access object storage using OpenStack CLI on CloudFerro Cloud[🔗](#how-to-access-object-storage-using-openstack-cli-on-brand-name "Permalink to this headline")
|
||||
=====================================================================================================================================================================
|
||||
|
||||
Cloud computing offers the ability to handle large chunks of data, directly on the remote server. OpenStack module [Swift](https://docs.openstack.org/swift/latest/) was created expressly to enable access to unstructured data that can grow without bounds, with the following design goals in mind :
|
||||
@ -10,7 +10,7 @@ Cloud computing offers the ability to handle large chunks of data, directly on t
|
||||
|
||||
**Swift** is installed as an independent module but on the syntax level, it is used through the parameters of **openstack** command.
|
||||
|
||||
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 install Swift
|
||||
@ -18,7 +18,7 @@ What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this h
|
||||
> * Basic openstack operations with containers
|
||||
> * Basic openstack operations with objects
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Hosting**
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
How to Backup an Instance and Download it to the Desktop on CloudFerro Cloud OpenStack Hosting[](#how-to-backup-an-instance-and-download-it-to-the-desktop-on-brand-name-openstack-hosting "Permalink to this headline")
|
||||
How to Backup an Instance and Download it to the Desktop on CloudFerro Cloud OpenStack Hosting[🔗](#how-to-backup-an-instance-and-download-it-to-the-desktop-on-brand-name-openstack-hosting "Permalink to this headline")
|
||||
=========================================================================================================================================================================================================================
|
||||
|
||||
First, you will need to setup the OpenStack CLI environment on the computer to which you want to download your instance. Depending on the operating system you are using, follow one of the links below:
|
||||
@ -14,7 +14,7 @@ Assume that you are
|
||||
|
||||

|
||||
|
||||
List Instances in Your Project[](#list-instances-in-your-project "Permalink to this headline")
|
||||
List Instances in Your Project[🔗](#list-instances-in-your-project "Permalink to this headline")
|
||||
-----------------------------------------------------------------------------------------------
|
||||
|
||||
List instances in your project using the following CLI command:
|
||||
@ -31,7 +31,7 @@ This will be the result:
|
||||
| ID | Name | Status | Networks | Image | Flavor |
|
||||
| 72170eb7-cee4-41a3-beea-c7d208446130 | vm-john-01 | ACTIVE | test\_network=192.168.2.172, 64.225.128.53 | Ubuntu 20.04 LTS | eo1.medium |
|
||||
|
||||
Create a Backup[](#create-a-backup "Permalink to this headline")
|
||||
Create a Backup[🔗](#create-a-backup "Permalink to this headline")
|
||||
-----------------------------------------------------------------
|
||||
|
||||
Now you can create a backup from command line interface (CLI) in the terminal (replace **72170eb7-cee4-41a3-beea-c7d208446130** with the ID of your instance):
|
||||
@ -72,7 +72,7 @@ The result would be:
|
||||
|
||||
```
|
||||
|
||||
Download the Backup File[](#download-the-backup-file "Permalink to this headline")
|
||||
Download the Backup File[🔗](#download-the-backup-file "Permalink to this headline")
|
||||
-----------------------------------------------------------------------------------
|
||||
|
||||
Disk image is a raw copy of the hard drive of your virtual machine. You can download it using the following command (replace **72170eb7-cee4-41a3-beea-c7d208446130** with the ID of your disk image):
|
||||
@ -82,7 +82,7 @@ user@ubuntu:~$ openstack image save --file backup-on-the-desktop 747d720d-a6f4-4
|
||||
|
||||
```
|
||||
|
||||
Upload the Backed Up File[](#upload-the-backed-up-file "Permalink to this headline")
|
||||
Upload the Backed Up File[🔗](#upload-the-backed-up-file "Permalink to this headline")
|
||||
-------------------------------------------------------------------------------------
|
||||
|
||||
After that, you can upload backup of your file using the Horizon dashboard:
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
How to create a set of VMs using OpenStack Heat Orchestration on CloudFerro Cloud[](#how-to-create-a-set-of-vms-using-openstack-heat-orchestration-on-brand-name "Permalink to this headline")
|
||||
How to create a set of VMs using OpenStack Heat Orchestration on CloudFerro Cloud[🔗](#how-to-create-a-set-of-vms-using-openstack-heat-orchestration-on-brand-name "Permalink to this headline")
|
||||
===============================================================================================================================================================================================
|
||||
|
||||
Heat is an OpenStack component responsible for Orchestration. Its purpose is to deliver automation engine and optimize processes.
|
||||
|
||||
Heat receives commands through templates which are text files in *yaml* format. A template describes the entire infrastructure that you want to deploy. The deployed environment is called a *stack* and can consist of any combination out of the **102** different resources that are available in OpenStack.
|
||||
|
||||
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")
|
||||
---------------------------------------------------------------------------------------
|
||||
|
||||
> * Typical parts of a Heat template
|
||||
@ -15,7 +15,7 @@ What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this h
|
||||
> * Using Heat with GUI
|
||||
> * More advanced template for Heat
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Account**
|
||||
@ -28,7 +28,7 @@ If you want to use Heat through CLI commands, Python must be installed and its v
|
||||
|
||||
If you have never installed one of the OpenStack clients, see :[How To Install OpenStack and Magnum Clients for Command Line Interface to CloudFerro Cloud Horizon](../kubernetes/How-To-Install-OpenStack-and-Magnum-Clients-for-Command-Line-Interface-to-CloudFerro-Cloud-Horizon.html.md).
|
||||
|
||||
Always use the latest value of image id[](#always-use-the-latest-value-of-image-id "Permalink to this headline")
|
||||
Always use the latest value of image id[🔗](#always-use-the-latest-value-of-image-id "Permalink to this headline")
|
||||
-----------------------------------------------------------------------------------------------------------------
|
||||
|
||||
From time to time, the default images of operating systems in the CloudFerro Cloud cloud are upgraded to the new versions. As a consequence, their **image id** will change. Let’s say that the image id for Ubuntu 20.04 LTS was **574fe1db-8099-4db4-a543-9e89526d20ae** at the time of writing of this article. While working through the article, you would normally take the **current** value of image id, and would use it to replace **574fe1db-8099-4db4-a543-9e89526d20ae** throughout the text.
|
||||
@ -39,7 +39,7 @@ Warning
|
||||
|
||||
Make sure that your automation code is using the **current value** of an OS image id, not the hardcoded one.
|
||||
|
||||
Basic template for using Heat[](#basic-template-for-using-heat "Permalink to this headline")
|
||||
Basic template for using Heat[🔗](#basic-template-for-using-heat "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------------------
|
||||
|
||||
Using the following snippet, you can create one virtual machine, booted from ephemeral disk. Create a text file called **template.yaml** with your favorite text editor and save it to disk:
|
||||
@ -67,7 +67,7 @@ Important
|
||||
|
||||
*Yaml* format does not allow for tabs, you must enter spaces instead.
|
||||
|
||||
Typical parts of a Heat template[](#typical-parts-of-a-heat-template "Permalink to this headline")
|
||||
Typical parts of a Heat template[🔗](#typical-parts-of-a-heat-template "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------------------------
|
||||
|
||||
Here are the basic elements of a Heat template:
|
||||
@ -91,7 +91,7 @@ Note
|
||||
|
||||
Your account will normally have a network starting with **cloud\_** but it may also have other networks. In the following examples, we use network called **eodata\_** as an example of an additional network that can be added while creating and using Heat templates.
|
||||
|
||||
How to get data for Heat template[](#how-to-get-data-for-heat-template "Permalink to this headline")
|
||||
How to get data for Heat template[🔗](#how-to-get-data-for-heat-template "Permalink to this headline")
|
||||
-----------------------------------------------------------------------------------------------------
|
||||
|
||||
Templates need data for images, flavor networks, key pairs, security groups and so on. You would normally know all these elements in advance, or you could “look around” at various parts of OpenStack environment:
|
||||
@ -109,7 +109,7 @@ You can work with Heat in two ways:
|
||||
> * through Command Line Interface (CLI), with **python-heatclient** preinstalled and
|
||||
> * interactively, through Horizon commands.
|
||||
|
||||
Using Heat with CLI[](#using-heat-with-cli "Permalink to this headline")
|
||||
Using Heat with CLI[🔗](#using-heat-with-cli "Permalink to this headline")
|
||||
-------------------------------------------------------------------------
|
||||
|
||||
Assuming you have
|
||||
@ -152,7 +152,7 @@ A new instance would be created under **Compute** -> **Instances**:
|
||||
|
||||

|
||||
|
||||
Using Heat with GUI[](#using-heat-with-gui "Permalink to this headline")
|
||||
Using Heat with GUI[🔗](#using-heat-with-gui "Permalink to this headline")
|
||||
-------------------------------------------------------------------------
|
||||
|
||||
Log in to the Horizon dashboard, choose **Orchestration** and then **Stacks** tab:
|
||||
@ -183,7 +183,7 @@ By creating a stack in Horizon you have also executed that template. The result
|
||||
|
||||
We end up with two stacks and two new instances, once using a CLI and the other time, using a GUI.
|
||||
|
||||
Create four VMs using an advanced Heat template[](#create-four-vms-using-an-advanced-heat-template "Permalink to this headline")
|
||||
Create four VMs using an advanced Heat template[🔗](#create-four-vms-using-an-advanced-heat-template "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
In the following example we will attach parameters and then create ResourceGroup with counter, a VM booted from Cinder Volume and several predefined outputs. In parameter **count** we state that we want to generate **4** instances at once, which will yield us the automation that we wanted in the first place. Save the following code as **template4.yaml**:
|
||||
@ -298,7 +298,7 @@ Under **Compute** -> **Instance** you would see five new instances created:
|
||||
|
||||
Four of them have names *my\_vm0*, *my\_vm1*, *my\_vm1* and *my\_vm1*, as defined in line **name: my\_vm%index%** in the template. The fifth is called **four-With\_volume-lrejw222kfvi**. Its name starts the same as the name of the template itself while the rest is automatically generated.
|
||||
|
||||
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 write your own templates as *yaml* files or you can use option **Orchestration** -> **Template Generator**, which will enable you to enter components in an interactive way:
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
How to create instance snapshot using OpenStack CLI on CloudFerro Cloud[](#how-to-create-instance-snapshot-using-openstack-cli-on-brand-name "Permalink to this headline")
|
||||
How to create instance snapshot using OpenStack CLI on CloudFerro Cloud[🔗](#how-to-create-instance-snapshot-using-openstack-cli-on-brand-name "Permalink to this headline")
|
||||
===========================================================================================================================================================================
|
||||
|
||||
In this article, you will learn how to create instance snapshot on CloudFerro Cloud cloud, using OpenStack CLI.
|
||||
@ -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,10 +25,10 @@ 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")
|
||||
---------------------------------------------------------------------------------------
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
How to install OpenStackClient GitBash for Windows on CloudFerro Cloud[](#how-to-install-openstackclient-gitbash-for-windows-on-brand-name "Permalink to this headline")
|
||||
How to install OpenStackClient GitBash for Windows on CloudFerro Cloud[🔗](#how-to-install-openstackclient-gitbash-for-windows-on-brand-name "Permalink to this headline")
|
||||
=========================================================================================================================================================================
|
||||
|
||||
In this tutorial, you start with a standard Windows installation, then install the OpenStack CLI client and end up connecting to your project on CloudFerro Cloud cloud.
|
||||
@ -8,7 +8,7 @@ In this tutorial, you start with a standard Windows installation, then install t
|
||||
* using Git Bash is simpler than using Windows Subsystem for Linux and is
|
||||
* providing a more straightforward access to your local file system.
|
||||
|
||||
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 the required software (Python 3, PIP, Git for Windows and the appropriate compilers)
|
||||
@ -17,7 +17,7 @@ What We Are Going To Cover[](#what-we-are-going-to-cover "Permalink to this h
|
||||
> * Authenticating the OpenStack CLI client to the cloud
|
||||
> * Executing a simple command to test whether the process was successful
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Hosting**
|
||||
@ -42,7 +42,7 @@ You need to download the RC file from your Horizon dashboard. To do that, follow
|
||||
|
||||
This file must be present on the machine on which you intend to use the OpenStack CLI client.
|
||||
|
||||
Step 1: Download and Install Python[](#step-1-download-and-install-python "Permalink to this headline")
|
||||
Step 1: Download and Install Python[🔗](#step-1-download-and-install-python "Permalink to this headline")
|
||||
--------------------------------------------------------------------------------------------------------
|
||||
|
||||
There are two ways of obtaining Python on CloudFerro Cloud cloud:
|
||||
@ -90,7 +90,7 @@ Open Windows command prompt and execute **python** command in it to check whethe
|
||||
|
||||
Close the command prompt.
|
||||
|
||||
Step 2: Install Git Bash and pip[](#step-2-install-git-bash-and-pip "Permalink to this headline")
|
||||
Step 2: Install Git Bash and pip[🔗](#step-2-install-git-bash-and-pip "Permalink to this headline")
|
||||
--------------------------------------------------------------------------------------------------
|
||||
|
||||
Git Bash for Windows is a set of programs that emulates Linux terminal, allowing you to use common Linux commands **ls**, **source**, **mv** and others.
|
||||
@ -107,7 +107,7 @@ Other programs in the suite are Git CMD, Git GUI etc.
|
||||
|
||||
The installation of Python and its suite of programs requires you to additionally install **pip** and update the necessary PythonSSL certificates.
|
||||
|
||||
Step 3: Install pip and update the PythonSSL certificates[](#step-3-install-pip-and-update-the-pythonssl-certificates "Permalink to this headline")
|
||||
Step 3: Install pip and update the PythonSSL certificates[🔗](#step-3-install-pip-and-update-the-pythonssl-certificates "Permalink to this headline")
|
||||
----------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
**pip** is a tool for managing and installing Python images.
|
||||
@ -140,7 +140,7 @@ pip install -U requests[security]
|
||||
|
||||

|
||||
|
||||
Step 4: Install Microsoft C++ Build Tools[](#step-4-install-microsoft-c-build-tools "Permalink to this headline")
|
||||
Step 4: Install Microsoft C++ Build Tools[🔗](#step-4-install-microsoft-c-build-tools "Permalink to this headline")
|
||||
------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Microsoft C++ Build Tools are required to install the OpenStack CLI client using **pip** on Windows.
|
||||
@ -161,7 +161,7 @@ The installation process might take a long time.
|
||||
|
||||
Reboot your computer if the installer prompts you to do so.
|
||||
|
||||
Step 5: Install virtualenv and the OpenStack CLI client[](#step-5-install-virtualenv-and-the-openstack-cli-client "Permalink to this headline")
|
||||
Step 5: Install virtualenv and the OpenStack CLI client[🔗](#step-5-install-virtualenv-and-the-openstack-cli-client "Permalink to this headline")
|
||||
------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
**virtualenv** allows you to perform Python operations in an isolated environment. In order to install it, open Git Bash if you previously closed it or rebooted your computer, and execute the following command:
|
||||
@ -202,7 +202,7 @@ From now on, the name of your isolated environment - **openstack\_cli** - will b
|
||||
|
||||
Closing the terminal and reopening will drop you from that environment.
|
||||
|
||||
### How Git Bash terminal commands differ from those in Windows[](#how-git-bash-terminal-commands-differ-from-those-in-windows "Permalink to this headline")
|
||||
### How Git Bash terminal commands differ from those in Windows[🔗](#how-git-bash-terminal-commands-differ-from-those-in-windows "Permalink to this headline")
|
||||
|
||||
In GitBash, there are two ways of inserting text from clipboard:
|
||||
|
||||
@ -213,7 +213,7 @@ The usual Windows commands such as **CTRL+V** or **CTRL+Shift+V**, **won’t wor
|
||||
|
||||
Git Bash emulates UNIX-based systems so while you are in it, use forward slashes and not the typical Windows backward slashes.
|
||||
|
||||
Step 6: Download and prepare jq[](#step-6-download-and-prepare-jq "Permalink to this headline")
|
||||
Step 6: Download and prepare jq[🔗](#step-6-download-and-prepare-jq "Permalink to this headline")
|
||||
------------------------------------------------------------------------------------------------
|
||||
|
||||
To authenticate the OpenStack CLI client in the next step, a program called **jq** will be needed. It is a JSON preprocessor, running from command line. To install, navigate to <https://jqlang.github.io/jq/download/> using your Internet browser.
|
||||
@ -231,7 +231,7 @@ mv jq.exe /usr/bin
|
||||
|
||||
This should allow you to use **jq** with the RC file easily.
|
||||
|
||||
Step 7: Install and configure the OpenStack CLI client[](#step-7-install-and-configure-the-openstack-cli-client "Permalink to this headline")
|
||||
Step 7: Install and configure the OpenStack CLI client[🔗](#step-7-install-and-configure-the-openstack-cli-client "Permalink to this headline")
|
||||
----------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Without leaving Git Bash, while still inside the **openstack\_cli** virtual environment, execute the following command:
|
||||
@ -269,7 +269,7 @@ openstack server list
|
||||
|
||||
The output should contain a table containing virtual machines from your project.
|
||||
|
||||
Reentering the Isolated Python Environment[](#reentering-the-isolated-python-environment "Permalink to this headline")
|
||||
Reentering the Isolated Python Environment[🔗](#reentering-the-isolated-python-environment "Permalink to this headline")
|
||||
-----------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
To run the OpenStack CLI client again, say, after you might have closed the Git Bash window, or have had shut down or restarted Windows, you would have to repeat the same commands you entered above (replace **C:/Users/Administrator** with the path containing your **openstack\_cli** folder).
|
||||
@ -284,7 +284,7 @@ After that, execute the **source** command on your RC file in the same way as pr
|
||||
|
||||
You can also create a batch file to automate reentering the Python environment.
|
||||
|
||||
What To Do Next[](#what-to-do-next "Permalink to this headline")
|
||||
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
|
||||
-----------------------------------------------------------------
|
||||
|
||||
The article [How To Install OpenStack and Magnum Clients for Command Line Interface to CloudFerro Cloud Horizon](../kubernetes/How-To-Install-OpenStack-and-Magnum-Clients-for-Command-Line-Interface-to-CloudFerro-Cloud-Horizon.html.md) will give you another procedure to install CLI and connect it to the cloud. It also contains several examples of using the CLI commands.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
How to install OpenStackClient for Linux on CloudFerro Cloud[](#how-to-install-openstackclient-for-linux-on-brand-name "Permalink to this headline")
|
||||
How to install OpenStackClient for Linux on CloudFerro Cloud[🔗](#how-to-install-openstackclient-for-linux-on-brand-name "Permalink to this headline")
|
||||
=====================================================================================================================================================
|
||||
|
||||
The OpenStack CLI client allows you to manage OpenStack environments using the command line interface. Its functions include:
|
||||
@ -15,7 +15,7 @@ This article covers two methods of installing this piece of software on Ubuntu.
|
||||
> * needing more advanced features than what Ubuntu packages provide and
|
||||
> * having to use the OpenStack CLI client on a Linux distribution which does not support the installation method described in the first method.
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Hosting**
|
||||
|
||||
@ -1,17 +1,17 @@
|
||||
How to install OpenStackClient on Windows using Windows Subsystem for Linux on CloudFerro Cloud OpenStack Hosting[](#how-to-install-openstackclient-on-windows-using-windows-subsystem-for-linux-on-brand-name-openstack-hosting "Permalink to this headline")
|
||||
How to install OpenStackClient on Windows using Windows Subsystem for Linux on CloudFerro Cloud OpenStack Hosting[🔗](#how-to-install-openstackclient-on-windows-using-windows-subsystem-for-linux-on-brand-name-openstack-hosting "Permalink to this headline")
|
||||
===============================================================================================================================================================================================================================================================
|
||||
|
||||
In this tutorial, you will control your OpenStack environment in a deeper and more precise way using the CLI (Command Line Interface). Of course, you can use the Horizon GUI (Graphical User Interface) running in your browser, but the CLI includes additional features like the ability to use scripts for more automated management of your environment.
|
||||
|
||||
The instructions for installing Windows Subsystem for Linux are based on the official Windows documentation found at <https://learn.microsoft.com/en-us/windows/wsl/>.
|
||||
|
||||
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 Windows Subsystem for Linux on Microsoft Windows
|
||||
> * Installing the OpenStack CLI client and authenticating
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Hosting**
|
||||
@ -30,14 +30,14 @@ No. 3 **Optional – software for 2FA authentication**
|
||||
|
||||
Your account at CloudFerro Cloud cloud may have two-factor authentication enabled. It means that apart from the usual username and password combination, you also need software to generate the TOTP – the six-digit code for the additional, second step of authentication. This article will provide additional technical details: [How to activate OpenStack CLI access to CloudFerro Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-OpenStack-CLI-access-to-CloudFerro-Cloud-cloud-using-one-or-two-factor-authentication.html.md).
|
||||
|
||||
Step 1: Check the version of Windows[](#step-1-check-the-version-of-windows "Permalink to this headline")
|
||||
Step 1: Check the version of Windows[🔗](#step-1-check-the-version-of-windows "Permalink to this headline")
|
||||
----------------------------------------------------------------------------------------------------------
|
||||
|
||||
Right-click on your start menu and left-click “System”.
|
||||
|
||||
A screen will appear in which you will see the version of your Microsoft Windows operating system. Memorize it or write it somewhere down.
|
||||
|
||||
Step 2: Install Ubuntu on Windows Subsystem for Linux[](#step-2-install-ubuntu-on-windows-subsystem-for-linux "Permalink to this headline")
|
||||
Step 2: Install Ubuntu on Windows Subsystem for Linux[🔗](#step-2-install-ubuntu-on-windows-subsystem-for-linux "Permalink to this headline")
|
||||
--------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Note
|
||||
@ -158,7 +158,7 @@ Wait for a short time. Eventually your Linux environment will be ready:
|
||||
|
||||

|
||||
|
||||
Step 3: Install OpenStack CLI in an isolated Python environment[](#step-3-install-openstack-cli-in-an-isolated-python-environment "Permalink to this headline")
|
||||
Step 3: Install OpenStack CLI in an isolated Python environment[🔗](#step-3-install-openstack-cli-in-an-isolated-python-environment "Permalink to this headline")
|
||||
----------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Now that you have installed Windows Subsystem on Linux running Ubuntu on your Windows computer, it is time to install OpenStack CLI.
|
||||
@ -216,7 +216,7 @@ If the command shows its output using a pager, you should be able to use the arr
|
||||
|
||||
If everything seems to work, time to move to the next step - authentication to your user account on CloudFerro Cloud.
|
||||
|
||||
Step 4: Download your OpenStack RC File[](#step-4-download-your-openstack-rc-file "Permalink to this headline")
|
||||
Step 4: Download your OpenStack RC File[🔗](#step-4-download-your-openstack-rc-file "Permalink to this headline")
|
||||
----------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Login to CloudFerro Cloud hosting account with Horizon interface <https://horizon.cloudferro.com>.
|
||||
@ -229,7 +229,7 @@ If your account has two factor authentication enabled, click the option **OpenSt
|
||||
|
||||
The RC file will be downloaded. Memorize or write somewhere down the name of that file. Move this file to the root location of your **C:** drive.
|
||||
|
||||
Step 5: Move the RC file to your Ubuntu environment[](#step-5-move-the-rc-file-to-your-ubuntu-environment "Permalink to this headline")
|
||||
Step 5: Move the RC file to your Ubuntu environment[🔗](#step-5-move-the-rc-file-to-your-ubuntu-environment "Permalink to this headline")
|
||||
----------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Return to your **Ubuntu** window.
|
||||
@ -268,7 +268,7 @@ openstack server list
|
||||
|
||||
```
|
||||
|
||||
How to run this environment later?[](#how-to-run-this-environment-later "Permalink to this headline")
|
||||
How to run this environment later?[🔗](#how-to-run-this-environment-later "Permalink to this headline")
|
||||
------------------------------------------------------------------------------------------------------
|
||||
|
||||
If you close the window with Ubuntu and reopen it, you will see that you are no longer in the **openstack\_cli** environment you created and thus no longer have access to OpenStack. You will need to reenter the **openstack\_cli** environment and reauthenticate.
|
||||
@ -289,7 +289,7 @@ source main-openrc.sh
|
||||
|
||||
Type your password and press Enter. You should now be able execute the OpenStack CLI commands as usual.
|
||||
|
||||
What To Do Next[](#what-to-do-next "Permalink to this headline")
|
||||
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
|
||||
-----------------------------------------------------------------
|
||||
|
||||
After installing the OpenStack CLI client and activating your new RC file, you can use other articles to perform operations on CloudFerro Cloud cloud:
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
How to move data volume between VMs using OpenStack CLI on CloudFerro Cloud[](#how-to-move-data-volume-between-vms-using-openstack-cli-on-brand-name "Permalink to this headline")
|
||||
How to move data volume between VMs using OpenStack CLI on CloudFerro Cloud[🔗](#how-to-move-data-volume-between-vms-using-openstack-cli-on-brand-name "Permalink to this headline")
|
||||
===================================================================================================================================================================================
|
||||
|
||||
Volumes are used to store data and those data can be accessed from a virtual machine to which the volume is attached. To access data stored on a volume from another virtual machine, you need to disconnect that volume from virtual machine to which it is currently connected, and connect it to another instance.
|
||||
|
||||
This article uses OpenStack CLI client to transfer volumes between virtual machines which are in the same project.
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Hosting**
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
How to share private container from object storage to another user on CloudFerro Cloud[](#how-to-share-private-container-from-object-storage-to-another-user-on-brand-name "Permalink to this headline")
|
||||
How to share private container from object storage to another user on CloudFerro Cloud[🔗](#how-to-share-private-container-from-object-storage-to-another-user-on-brand-name "Permalink to this headline")
|
||||
=========================================================================================================================================================================================================
|
||||
|
||||
You can create your own private containers in Object Store of your projects and you can grant access to other users.
|
||||
@ -9,7 +9,7 @@ The project can be in one or more domains.
|
||||
|
||||
Otherwise, if users are members of the same project, they see all containers in that project and you cannot limit access to specific containers.
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Hosting**
|
||||
@ -32,7 +32,7 @@ The OpenStack Object Store module, known as *Swift*, allows you to store and ret
|
||||
|
||||
See [How to access object storage using OpenStack CLI on CloudFerro Cloud](How-to-access-object-storage-using-OpenStack-CLI-on-CloudFerro-Cloud.html.md)
|
||||
|
||||
Setting up the test example[](#setting-up-the-test-example "Permalink to this headline")
|
||||
Setting up the test example[🔗](#setting-up-the-test-example "Permalink to this headline")
|
||||
-----------------------------------------------------------------------------------------
|
||||
|
||||
In the example below there are three projects:
|
||||
@ -76,7 +76,7 @@ The user “owner” has three containers in their project “main”…
|
||||
|
||||
In the example below, the user “owner” will grant “read only” access to container “c-main-a” for “user\_1”
|
||||
|
||||
Download the RC file to share permissions with users[](#download-the-rc-file-to-share-permissions-with-users "Permalink to this headline")
|
||||
Download the RC file to share permissions with users[🔗](#download-the-rc-file-to-share-permissions-with-users "Permalink to this headline")
|
||||
-------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Firstly, the user “owner” should login to their domain if they didn’t do it yet:
|
||||
@ -138,7 +138,7 @@ export OS_USER_DOMAIN_NAME="cloud_00373" # ****IF THIS LINE IS MISSING IN YOUR F
|
||||
|
||||
```
|
||||
|
||||
Sharing the RC file with the users[](#sharing-the-rc-file-with-the-users "Permalink to this headline")
|
||||
Sharing the RC file with the users[🔗](#sharing-the-rc-file-with-the-users "Permalink to this headline")
|
||||
-------------------------------------------------------------------------------------------------------
|
||||
|
||||
Copy the file **main-openrc.sh** to your CLI directory.
|
||||
@ -186,7 +186,7 @@ export OS_USER_DOMAIN_NAME="cloud_00373" # ****IF THIS LINE IS MISSING IN YOUR F
|
||||
|
||||
The called “user\_2” should do the same procedure as above.
|
||||
|
||||
Owner sources the RC file[](#owner-sources-the-rc-file "Permalink to this headline")
|
||||
Owner sources the RC file[🔗](#owner-sources-the-rc-file "Permalink to this headline")
|
||||
-------------------------------------------------------------------------------------
|
||||
|
||||
Now, each user should open their terminal and source the openrc file:
|
||||
@ -204,7 +204,7 @@ c-main-d
|
||||
|
||||
```
|
||||
|
||||
User\_1 sources the RC file[](#user-1-sources-the-rc-file "Permalink to this headline")
|
||||
User\_1 sources the RC file[🔗](#user-1-sources-the-rc-file "Permalink to this headline")
|
||||
----------------------------------------------------------------------------------------
|
||||
|
||||
terminal of user “user\_1”:
|
||||
@ -220,7 +220,7 @@ c-project_1-b
|
||||
|
||||
```
|
||||
|
||||
User\_2 sources the RC file[](#user-2-sources-the-rc-file "Permalink to this headline")
|
||||
User\_2 sources the RC file[🔗](#user-2-sources-the-rc-file "Permalink to this headline")
|
||||
----------------------------------------------------------------------------------------
|
||||
|
||||
terminal of user “user\_2”:
|
||||
@ -235,7 +235,7 @@ c-project_2-b
|
||||
|
||||
```
|
||||
|
||||
Uploading of test files[](#uploading-of-test-files "Permalink to this headline")
|
||||
Uploading of test files[🔗](#uploading-of-test-files "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------
|
||||
|
||||
The user “owner” prepares and uploads test files:
|
||||
@ -312,7 +312,7 @@ X-Container-Bytes-Used-Actual: 8192
|
||||
|
||||
```
|
||||
|
||||
Granting access[](#granting-access "Permalink to this headline")
|
||||
Granting access[🔗](#granting-access "Permalink to this headline")
|
||||
-----------------------------------------------------------------
|
||||
|
||||
Grant access to container “c-main-a” for user\_1:
|
||||
@ -372,7 +372,7 @@ Similar procedure can be used to grant “write” permission to “user\_1”:
|
||||
|
||||
```
|
||||
|
||||
What To Do Next[](#what-to-do-next "Permalink to this headline")
|
||||
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
|
||||
-----------------------------------------------------------------
|
||||
|
||||
These articles can also be of interest:
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
How to start a VM from instance snapshot using OpenStack CLI on CloudFerro Cloud[](#how-to-start-a-vm-from-instance-snapshot-using-openstack-cli-on-brand-name "Permalink to this headline")
|
||||
How to start a VM from instance snapshot using OpenStack CLI on CloudFerro Cloud[🔗](#how-to-start-a-vm-from-instance-snapshot-using-openstack-cli-on-brand-name "Permalink to this headline")
|
||||
=============================================================================================================================================================================================
|
||||
|
||||
In this article, you will learn how to create a virtual machine from an instance snapshot using OpenStack CLI client.
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
How to transfer volumes between domains and projects using OpenStack CLI client on CloudFerro Cloud[](#how-to-transfer-volumes-between-domains-and-projects-using-openstack-cli-client-on-brand-name "Permalink to this headline")
|
||||
How to transfer volumes between domains and projects using OpenStack CLI client on CloudFerro Cloud[🔗](#how-to-transfer-volumes-between-domains-and-projects-using-openstack-cli-client-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**
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
Resizing a virtual machine using OpenStack CLI on CloudFerro Cloud[](#resizing-a-virtual-machine-using-openstack-cli-on-brand-name "Permalink to this headline")
|
||||
Resizing a virtual machine using OpenStack CLI on CloudFerro Cloud[🔗](#resizing-a-virtual-machine-using-openstack-cli-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 CLI commands in OpenStack.
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Account**
|
||||
@ -37,7 +37,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.)
|
||||
@ -78,7 +78,7 @@ openstack server list
|
||||
|
||||
```
|
||||
|
||||
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")
|
||||
-------------------------------------------------------------------------------
|
||||
|
||||
To resize a VM with CLI, there is a general command
|
||||
@ -122,7 +122,7 @@ openstack server show ResizingCLI
|
||||
|
||||
to see the real state of the VM after confirmation. We will now see that the **status** is **ACTIVE**.
|
||||
|
||||
Reverting a resize[](#reverting-a-resize "Permalink to this headline")
|
||||
Reverting a resize[🔗](#reverting-a-resize "Permalink to this headline")
|
||||
-----------------------------------------------------------------------
|
||||
|
||||
Reverting a resize switches the VM back to its original flavor and cleans up temporary resources allocated during the resize operation.
|
||||
@ -136,7 +136,7 @@ openstack server resize revert ResizingCLI
|
||||
|
||||
If status is not **VERIFY\_RESIZE**, we will get message stating that it is not possible to revert resize while it is in an active state (HTTP 409). In that case, perform the “regular” resizing with **openstack server resize**.
|
||||
|
||||
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: /openstackcli/Resizing-a-virtual-machine-using-OpenStack-Horizon-on-CloudFerro-Cloud
|
||||
@ -1,9 +1,9 @@
|
||||
Use backup command to create rotating backups of virtual machines on CloudFerro Cloud cloud[](#use-backup-command-to-create-rotating-backups-of-virtual-machines-on-brand-name-cloud "Permalink to this headline")
|
||||
Use backup command to create rotating backups of virtual machines on CloudFerro Cloud cloud[🔗](#use-backup-command-to-create-rotating-backups-of-virtual-machines-on-brand-name-cloud "Permalink to this headline")
|
||||
===================================================================================================================================================================================================================
|
||||
|
||||
**Rotating backups** in OpenStack refer to a backup strategy where older backups are automatically deleted after a predefined number of backups are created. This ensures that storage does not grow indefinitely while still maintaining a set number of recent backups for disaster recovery.
|
||||
|
||||
The rotating backup algorithm[](#the-rotating-backup-algorithm "Permalink to this headline")
|
||||
The rotating backup algorithm[🔗](#the-rotating-backup-algorithm "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------------------
|
||||
|
||||
Creating rotating backups of virtual machines is a process comprising of the following steps:
|
||||
@ -17,7 +17,7 @@ Define rotation limit
|
||||
Delete older backups
|
||||
: Once the limit is reached, start deleting the existing backups, usually the oldest one.
|
||||
|
||||
backup create vs. image create[](#backup-create-vs-image-create "Permalink to this headline")
|
||||
backup create vs. image create[🔗](#backup-create-vs-image-create "Permalink to this headline")
|
||||
----------------------------------------------------------------------------------------------
|
||||
|
||||
There are two ways of creating backups under OpenStack, using one of these two commands:
|
||||
@ -26,7 +26,7 @@ There are two ways of creating backups under OpenStack, using one of these two c
|
||||
|
||||
Here is how they compare:
|
||||
|
||||
Table 3 Comparison of Backup and Image Creation Commands[](#id1 "Permalink to this table")
|
||||
Table 3 Comparison of Backup and Image Creation Commands[🔗](#id1 "Permalink to this table")
|
||||
|
||||
| Feature | `openstack server backup create` | `openstack server image create` |
|
||||
| --- | --- | --- |
|
||||
@ -42,7 +42,7 @@ Table 3 Comparison of Backup and Image Creation Commands[](#id1 "Permalink to
|
||||
|
||||
In this article we are going to use a **openstack server backup create** command under OpenStack to create rotating backups of virtual machines.
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
Use script to create daily weekly and monthly rotating backups of virtual machines on CloudFerro Cloud[](#use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-on-brand-name "Permalink to this headline")
|
||||
Use script to create daily weekly and monthly rotating backups of virtual machines on CloudFerro Cloud[🔗](#use-script-to-create-daily-weekly-and-monthly-rotating-backups-of-virtual-machines-on-brand-name "Permalink to this headline")
|
||||
=========================================================================================================================================================================================================================================
|
||||
|
||||
**Rotating backups** in OpenStack refer to a backup strategy where older backups are automatically deleted after a predefined number of backups are created. This ensures that storage does not grow indefinitely while still maintaining a set number of recent backups for disaster recovery.
|
||||
|
||||
backup create vs. image create[](#backup-create-vs-image-create "Permalink to this headline")
|
||||
backup create vs. image create[🔗](#backup-create-vs-image-create "Permalink to this headline")
|
||||
----------------------------------------------------------------------------------------------
|
||||
|
||||
There are two ways of creating backups under OpenStack, using one of these two commands:
|
||||
@ -12,7 +12,7 @@ There are two ways of creating backups under OpenStack, using one of these two c
|
||||
|
||||
Here is how they compare:
|
||||
|
||||
Table 4 Comparison of Backup and Image Creation Commands[](#id1 "Permalink to this table")
|
||||
Table 4 Comparison of Backup and Image Creation Commands[🔗](#id1 "Permalink to this table")
|
||||
|
||||
| Feature | `openstack server backup create` | `openstack server image create` |
|
||||
| --- | --- | --- |
|
||||
@ -28,7 +28,7 @@ Table 4 Comparison of Backup and Image Creation Commands[](#id1 "Permalink to
|
||||
|
||||
In this article, you will learn how to create multiple series of rotating backups with a script which uses multiple **OpenStackClient** commands to achieve this goal.
|
||||
|
||||
Prerequisites[](#prerequisites "Permalink to this headline")
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
@ -7,7 +7,7 @@
|
||||
* [How to backup an instance and download it to the desktop on CloudFerro Cloud](How-to-backup-an-instance-and-download-it-to-the-desktop-on-CloudFerro-Cloud.html.md)
|
||||
* [How to create a set of VMs using OpenStack Heat Orchestration on CloudFerro Cloud](How-to-create-a-set-of-VMs-using-OpenStack-Heat-Orchestration-on-CloudFerro-Cloud.html.md)
|
||||
* [How to create instance snapshot using OpenStack CLI on CloudFerro Cloud](How-to-create-instance-snapshot-using-OpenStack-CLI-on-CloudFerro-Cloud.html.md)
|
||||
* [How Git Bash terminal commands differ from those in Windows[](#how-git-bash-terminal-commands-differ-from-those-in-windows "Permalink to this headline")](How-to-install-OpenStackClient-GitBash-or-Cygwin-for-Windows-on-CloudFerro-Cloud.html.md)
|
||||
* [How Git Bash terminal commands differ from those in Windows[🔗](#how-git-bash-terminal-commands-differ-from-those-in-windows "Permalink to this headline")](How-to-install-OpenStackClient-GitBash-or-Cygwin-for-Windows-on-CloudFerro-Cloud.html.md)
|
||||
* [How to install OpenStackClient for Linux on CloudFerro Cloud](How-to-install-OpenStackClient-for-Linux-on-CloudFerro-Cloud.html.md)
|
||||
* [How to install OpenStackClient on Windows using Windows Subsystem for Linux on CloudFerro Cloud OpenStack Hosting](How-to-install-OpenStackClient-on-Windows-using-Windows-Subsystem-for-Linux-on-CloudFerro-Cloud-OpenStack-Hosting.html.md)
|
||||
* [How to move data volume between two VMs using OpenStack CLI on CloudFerro Cloud](How-to-move-data-volume-between-two-VMs-using-OpenStack-CLI-on-CloudFerro-Cloud.html.md)
|
||||
|
||||
Reference in New Issue
Block a user