brand changes have been done
This commit is contained in:
govardhan
@ -1,7 +1,7 @@
|
||||
Block storage and object storage performance limits on 3Engines Cloud[🔗](#block-storage-and-object-storage-performance-limits-on-brand-name "Permalink to this headline")
|
||||
Block storage and object storage performance limits on connectVM Cloud[🔗](#block-storage-and-object-storage-performance-limits-on-brand-name "Permalink to this headline")
|
||||
===========================================================================================================================================================================
|
||||
|
||||
On 3Engines Cloud, there are performance limits for **HDD**, **NVMe (SSD)**, and **Object Storage** to ensure stable operation and protect against accidental DDoS attacks.
|
||||
On connectVM 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")
|
||||
---------------------------------------------------------------
|
||||
@ -12,7 +12,7 @@ Block HDD
|
||||
Block SSD/NVMe
|
||||
: **3000** IOPS (read and write)
|
||||
|
||||
**NOTE**: On 3Engines Cloud, *all* SSD storage is NVMe-based.
|
||||
**NOTE**: On connectVM Cloud, *all* SSD storage is NVMe-based.
|
||||
|
||||
S3 Object Storage (General Tier)
|
||||
: **2000** operations per second with a
|
||||
@ -1,4 +1,4 @@
|
||||
DNS as a Service on 3Engines Cloud Hosting[🔗](#dns-as-a-service-on-brand-name-cloud-name-hosting "Permalink to this headline")
|
||||
DNS as a Service on connectVM 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:
|
||||
@ -16,9 +16,9 @@ DNS as a Service (DNSaaS) provides functionality of managing configuration of us
|
||||
| SSHFP | SSH Public Key Fingerprint |
|
||||
| TXT | Text record |
|
||||
|
||||
DNS configuration management is available via 3Engines web dashboard (Horizon), 3Engines command line interface as well as via the API.
|
||||
DNS configuration management is available via connectVM web dashboard (Horizon), connectVM command line interface as well as via the API.
|
||||
|
||||
DNS records management is performed on the level of an 3Engines project.
|
||||
DNS records management is performed on the level of an connectVM project.
|
||||
|
||||
Since DNSaaS purpose is to deal with external domain names, the internal name resolution (name resolution for private IP addresses within user’s projects) is not covered by this documentation.
|
||||
|
||||
@ -31,16 +31,16 @@ What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this
|
||||
> * Adding new record for the domain
|
||||
> * Adding records for subdomains
|
||||
> * Managing records
|
||||
> * Limitations in 3Engines DNSaaS
|
||||
> * Limitations in connectVM DNSaaS
|
||||
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with access to the Horizon interface: <https://console.connectvm.com/>.
|
||||
|
||||
No. 2 **Must have access to a project in 3Engines Cloud 3Engines account**
|
||||
No. 2 **Must have access to a project in connectVM Cloud connectVM account**
|
||||
|
||||
If you are a tenant manager, you will be able to either use the existing basic project or create new projects for yourself or your users.
|
||||
|
||||
@ -53,7 +53,7 @@ We assume you already have a
|
||||
> * basic knowledge of Domain Name Service principles as well as
|
||||
> * understanding of the purpose of DNS records.
|
||||
|
||||
If not, please see [DNS article on Wikipedia](https://en.wikipedia.org/wiki/Domain_Name_System) or [3Engines DNSaaS command line reference](https://docs.3Engines.org/python-designateclient/latest/user/shell-v2.html.md)
|
||||
If not, please see [DNS article on Wikipedia](https://en.wikipedia.org/wiki/Domain_Name_System) or [connectVM DNSaaS command line reference](https://docs.connectVM.org/python-designateclient/latest/user/shell-v2.html.md)
|
||||
|
||||
No. 4 **Must have domain purchased from a registrar**
|
||||
|
||||
@ -61,31 +61,31 @@ You also must own a domain purchased from any registrar (domain reseller). Obtai
|
||||
|
||||
No. 5 **Must have a Linux server with an assigned IP address**
|
||||
|
||||
To verify DNS creation and propagation, you shall use the **dig** command from Linux. You will also need an IP address to point the domain name to. You may have already created one such VM in your 3Engines Cloud server and if not, here is how to create a virtual machine, assign a floating IP to it and access it from Windows desktop computer:
|
||||
To verify DNS creation and propagation, you shall use the **dig** command from Linux. You will also need an IP address to point the domain name to. You may have already created one such VM in your connectVM Cloud server and if not, here is how to create a virtual machine, assign a floating IP to it and access it from Windows desktop computer:
|
||||
|
||||
[How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md)
|
||||
[How to create a Linux VM and access it from Windows desktop on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md)
|
||||
|
||||
Or, you might connect from a Linux based computer to the cloud:
|
||||
|
||||
[How to create a Linux VM and access it from Linux command line on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md)
|
||||
[How to create a Linux VM and access it from Linux command line on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md)
|
||||
|
||||
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")
|
||||
-------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
The configuration of domain name in your registrar’s system must point to the NS records of 3Engines name servers. It can be achieved in two ways:
|
||||
The configuration of domain name in your registrar’s system must point to the NS records of connectVM name servers. It can be achieved in two ways:
|
||||
|
||||
**Option 1 - Use 3Engines name servers (recommended)**
|
||||
**Option 1 - Use connectVM name servers (recommended)**
|
||||
|
||||
Configure NS records for your domain to the following 3Engines name servers:
|
||||
Configure NS records for your domain to the following connectVM name servers:
|
||||
|
||||
| | | |
|
||||
| --- | --- | --- |
|
||||
| Purpose | Name Server | IP |
|
||||
| primary name server | cloud-dns1.3Engines.com | 91.212.141.94 |
|
||||
| secondary name server | cloud-dns2.3Engines.com | 91.212.141.102 |
|
||||
| secondary name server | cloud-dns3.3Engines.com | 91.212.141.86 |
|
||||
| primary name server | cloud-dns1.connectVM.com | 91.212.141.94 |
|
||||
| secondary name server | cloud-dns2.connectVM.com | 91.212.141.102 |
|
||||
| secondary name server | cloud-dns3.connectVM.com | 91.212.141.86 |
|
||||
|
||||
**Option 2 - Set up your own glue records (not recommended)**
|
||||
|
||||
@ -107,7 +107,7 @@ Step 2 Zone configuration[🔗](#step-2-zone-configuration "Permalink to this he
|
||||
|
||||
Zone configuration is defining parameters for the main domain name you have purchased.
|
||||
|
||||
To manage domain *exampledomain.com* in 3Engines, login to 3Engines dashboard, choose the right project if different than default, go to **Project** → **DNS** → **Zones**, click **Create Zone** and fill in the required fields:
|
||||
To manage domain *exampledomain.com* in connectVM, login to connectVM dashboard, choose the right project if different than default, go to **Project** → **DNS** → **Zones**, click **Create Zone** and fill in the required fields:
|
||||
|
||||
|
||||
|
||||
@ -117,9 +117,9 @@ Here is what the parameters mean:
|
||||
> * **Description**: free text description
|
||||
> * **Email Address**: an administrative e-mail address associated with the domain
|
||||
> * **TTL**: *Time To Live* in seconds - a period of time between refreshing cache in DNS servers. Please note that the longer time, the faster will be name recognition for your domain by external DNS servers but also if you introduce changes, they will propagate slower. The default value of 3600 seconds is a reasonable compromise.
|
||||
> * **Type**: You may choose if 3Engines name servers will be primary or secondary for your domain. Default: Primary. In case you want to setup secondary name servers, you just define IP addresses or master DNS servers for the domain.
|
||||
> * **Type**: You may choose if connectVM name servers will be primary or secondary for your domain. Default: Primary. In case you want to setup secondary name servers, you just define IP addresses or master DNS servers for the domain.
|
||||
|
||||
After submitting, your domain should be served by 3Engines.
|
||||
After submitting, your domain should be served by connectVM.
|
||||
|
||||
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")
|
||||
-------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
@ -137,11 +137,11 @@ There are several ways of checking whether the domain name has propagated.
|
||||
: The **dig** command has several parameters. The following combination will show the presence of the name servers in the global DNS system:
|
||||
|
||||
> ```
|
||||
> dig -t any +noall +answer exampledomain.com @cloud-dns1.3Engines.com
|
||||
> exampledomain.com. 3600 IN SOA cloud-dns2.3Engines.com. [email protected]. 1675003306 3588 600 86400 3600
|
||||
> exampledomain.com. 3600 IN NS cloud-dns1.3Engines.com.
|
||||
> exampledomain.com. 3600 IN NS cloud-dns3.3Engines.com.
|
||||
> exampledomain.com. 3600 IN NS cloud-dns2.3Engines.com.
|
||||
> dig -t any +noall +answer exampledomain.com @cloud-dns1.connectVM.com
|
||||
> exampledomain.com. 3600 IN SOA cloud-dns2.connectVM.com. [email protected]. 1675003306 3588 600 86400 3600
|
||||
> exampledomain.com. 3600 IN NS cloud-dns1.connectVM.com.
|
||||
> exampledomain.com. 3600 IN NS cloud-dns3.connectVM.com.
|
||||
> exampledomain.com. 3600 IN NS cloud-dns2.connectVM.com.
|
||||
>
|
||||
> ```
|
||||
|
||||
@ -192,12 +192,12 @@ The parameters are:
|
||||
Submit the form and check whether your configuration works:
|
||||
|
||||
```
|
||||
dig -t any +noall +answer exampledomain.com @cloud-dns1.3Engines.com
|
||||
exampledomain.com. 3600 IN SOA cloud-dns2.3Engines.com. XXXXXXXXX.YYYYYYYY.com. 1675325538 3530 600 86400 3600
|
||||
dig -t any +noall +answer exampledomain.com @cloud-dns1.connectVM.com
|
||||
exampledomain.com. 3600 IN SOA cloud-dns2.connectVM.com. XXXXXXXXX.YYYYYYYY.com. 1675325538 3530 600 86400 3600
|
||||
exampledomain.com. 3600 IN A 64.225.133.254
|
||||
exampledomain.com. 3600 IN NS cloud-dns1.3Engines.com.
|
||||
exampledomain.com. 3600 IN NS cloud-dns2.3Engines.com.
|
||||
exampledomain.com. 3600 IN NS cloud-dns3.3Engines.com.
|
||||
exampledomain.com. 3600 IN NS cloud-dns1.connectVM.com.
|
||||
exampledomain.com. 3600 IN NS cloud-dns2.connectVM.com.
|
||||
exampledomain.com. 3600 IN NS cloud-dns3.connectVM.com.
|
||||
|
||||
```
|
||||
|
||||
@ -220,7 +220,7 @@ To configure an address of web server in **exampledomain.com**, so that **www.ex
|
||||
Submit the form and check whether your configuration works:
|
||||
|
||||
```
|
||||
dig -t any +noall +answer www.exampledomain.com @cloud-dns1.3Engines.com
|
||||
dig -t any +noall +answer www.exampledomain.com @cloud-dns1.connectVM.com
|
||||
www.exampledomain.com. 3600 IN A 64.225.133.254
|
||||
|
||||
```
|
||||
@ -228,7 +228,7 @@ www.exampledomain.com. 3600 IN A 64.225.133.254
|
||||
Step 6 Managing records[🔗](#step-6-managing-records "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------
|
||||
|
||||
Anytime you want to review, edit or delete records in your domain, visit 3Engines dashboard, **Project** → **DNS** → **Zones**. After clicking the domain name of your interest, choose **Record Sets** tab and see the list of all records:
|
||||
Anytime you want to review, edit or delete records in your domain, visit connectVM dashboard, **Project** → **DNS** → **Zones**. After clicking the domain name of your interest, choose **Record Sets** tab and see the list of all records:
|
||||
|
||||
|
||||
|
||||
@ -237,21 +237,21 @@ From this screen you can update or delete records.
|
||||
Limitations[🔗](#limitations "Permalink to this headline")
|
||||
---------------------------------------------------------
|
||||
|
||||
There are the following limitations in 3Engines DNSaaS:
|
||||
There are the following limitations in connectVM DNSaaS:
|
||||
|
||||
> * You cannot manage NS records for your domain. Therefore
|
||||
>
|
||||
> > + you cannot add additional secondary name servers
|
||||
> > + you are unable to delegate subdomains to external servers
|
||||
> * Even though you are able to configure reverse DNS for your domain, this configuration will have no effect since reverse DNS for 3Engines Cloud IP pools are managed on DNS servers other than 3Engines DNSaaS.
|
||||
> * Even though you are able to configure reverse DNS for your domain, this configuration will have no effect since reverse DNS for connectVM Cloud IP pools are managed on DNS servers other than connectVM DNSaaS.
|
||||
|
||||
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
|
||||
-----------------------------------------------------------------
|
||||
|
||||
Once an 3Engines object has floating IP address, you can use the DNS service to propagate a domain name and, thus, create a service or a site. There are several situations in which you can create a floating IP address:
|
||||
Once an connectVM object has floating IP address, you can use the DNS service to propagate a domain name and, thus, create a service or a site. There are several situations in which you can create a floating IP address:
|
||||
|
||||
You already have an existing VM
|
||||
: Follow the procedure in article [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md) to assign a new floating IP to it.
|
||||
: Follow the procedure in article [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md) to assign a new floating IP to it.
|
||||
|
||||
Assign floating IP while creating a new VM from scratch
|
||||
: That is the approach in articles from Prerequisite No. 5.
|
||||
@ -259,4 +259,4 @@ Assign floating IP while creating a new VM from scratch
|
||||
**Kubernetes services can have an automatically assigned floating IP**
|
||||
: The following article shows how to deploy an HTTPS service on Kubernetes:
|
||||
|
||||
[Deploying HTTPS Services on Magnum Kubernetes in 3Engines Cloud Cloud](../kubernetes/Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-3Engines-Cloud-Cloud.html.md)
|
||||
[Deploying HTTPS Services on Magnum Kubernetes in connectVM Cloud Cloud](../kubernetes/Deploying-HTTPS-Services-on-Magnum-Kubernetes-in-connectVM-Cloud-Cloud.html.md)
|
||||
@ -1,7 +1,7 @@
|
||||
Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud[🔗](#dashboard-overview-project-quotas-and-flavors-limits-on-brand-name "Permalink to this headline")
|
||||
Dashboard Overview – Project Quotas And Flavors Limits on connectVM Cloud[🔗](#dashboard-overview-project-quotas-and-flavors-limits-on-brand-name "Permalink to this headline")
|
||||
===============================================================================================================================================================================
|
||||
|
||||
While using 3Engines 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.
|
||||
While using connectVM 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.
|
||||
|
||||
On the first screen after logging into Horizon Dashboard you will see seven charts reflecting limits most essential to the stability of the platform. You can always show this screen with command **Compute** -> **Overview**.
|
||||
|
||||
@ -34,4 +34,4 @@ During the VM creation process, while choosing flavor, you may spot a yellow exc
|
||||
|
||||
You can expand the flavor summary by clicking the arrow on the left. The charts will show the current free resources as well as the resources that will remain after creating a new instance.
|
||||
|
||||
If the quota would be exceeded, 3Engines will non allow to choose this particular flavor.
|
||||
If the quota would be exceeded, connectVM will non allow to choose this particular flavor.
|
||||
@ -1,4 +1,4 @@
|
||||
How To Create a New Linux VM With NVIDIA Virtual GPU in the 3Engines Dashboard Horizon on 3Engines Cloud[🔗](#how-to-create-a-new-linux-vm-with-nvidia-virtual-gpu-in-the-3Engines-dashboard-horizon-on-brand-name "Permalink to this headline")
|
||||
How To Create a New Linux VM With NVIDIA Virtual GPU in the connectVM Dashboard Horizon on connectVM Cloud[🔗](#how-to-create-a-new-linux-vm-with-nvidia-virtual-gpu-in-the-connectVM-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
|
||||
@ -38,7 +38,7 @@ Insert the name of the instance (eg. “vm\_with\_vgpu”) and click Next button
|
||||
|
||||
Your goal is to use an image with predefinced NVIDIA support. To list all such images, click on field **Available** and enter ‘NVIDIA’ into it. Only the images with NVIDIA in their names will be listed:
|
||||
|
||||
|
||||
|
||||
|
||||
Select Instance Boot Source (eg. “Image”), and choose desired image (eg. “Ubuntu 20.04 NVIDIA”) by clicking on arrow.
|
||||
|
||||
@ -88,7 +88,7 @@ Open “Security Groups” After that, choose “allow\_ping\_ssh\_icmp\_rdp”
|
||||
|
||||
|
||||
|
||||
Choose or generate SSH keypair, as explained in article [How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md) for your VM. Next, launch your instance by clicking on blue button.
|
||||
Choose or generate SSH keypair, as explained in article [How to create key pair in connectVM Dashboard on connectVM Cloud](How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md) for your VM. Next, launch your instance by clicking on blue button.
|
||||
|
||||
|
||||
|
||||
@ -98,7 +98,7 @@ You will see “Instances” menu with your newly created VM.
|
||||
|
||||
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 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md)
|
||||
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 connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md)
|
||||
|
||||
Step 4 Issue Commands from the Console[🔗](#step-4-issue-commands-from-the-console "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------------------------------------
|
||||
@ -107,9 +107,9 @@ Open the drop-down menu and choose “Console”.
|
||||
|
||||
|
||||
|
||||
You can connect to your virtual machine using SSH, see this article: [How to connect to your virtual machine via SSH in Linux on 3Engines Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md)
|
||||
You can connect to your virtual machine using SSH, see this article: [How to connect to your virtual machine via SSH in Linux on connectVM Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md)
|
||||
|
||||
You can also use the SPICE console using the 3Engines Dashboard.
|
||||
You can also use the SPICE console using the connectVM Dashboard.
|
||||
|
||||
Click on the black terminal area (to activate access to the console). Type:
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
How to access the VM from 3Engines console on 3Engines Cloud[🔗](#how-to-access-the-vm-from-3Engines-console-on-brand-name "Permalink to this headline")
|
||||
How to access the VM from connectVM console on connectVM Cloud[🔗](#how-to-access-the-vm-from-connectVM-console-on-brand-name "Permalink to this headline")
|
||||
===========================================================================================================================================================
|
||||
|
||||
Once you have created a virtual machine in 3Engines, you will need to perform various administrative tasks such as:
|
||||
Once you have created a virtual machine in connectVM, you will need to perform various administrative tasks such as:
|
||||
|
||||
> * installing and uninstalling software,
|
||||
> * uploading and downloading files,
|
||||
@ -32,14 +32,14 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with access to the Horizon interface: <https://console.connectvm.com/>.
|
||||
|
||||
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://3engine.rootxwire.com/> and select your authentication method:
|
||||
1. Go to <https://console.connectvm.com/> and select your authentication method:
|
||||
|
||||
|
||||
|
||||
|
||||
You will enter the Horizon main screen.
|
||||
|
||||
@ -72,7 +72,7 @@ You will then use the console as a predefined user called **eouser**.
|
||||
|
||||
Attention
|
||||
|
||||
Google Chrome seems to work slowly while using the 3Engines console. Firefox works well.
|
||||
Google Chrome seems to work slowly while using the connectVM console. Firefox works well.
|
||||
|
||||
Using console to perform administrative tasks within Fedora VMs[🔗](#using-console-to-perform-administrative-tasks-within-fedora-vms "Permalink to this headline")
|
||||
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
@ -96,11 +96,11 @@ where *vault* is the namespace within which the pod *vault-0* will be found and
|
||||
|
||||
Further explanations of **exec** command are out of scope of this article. The following article will show you how to activate the **kubectl** command after the cluster has been created:
|
||||
|
||||
[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md)
|
||||
[How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md)
|
||||
|
||||
This article shows an example of an **exec** command to enter the VM and, later, save the data within it:
|
||||
|
||||
[Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on 3Engines Cloud 3Engines Magnum](../kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-3Engines-Cloud-3Engines-Magnum.html.md)
|
||||
[Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on connectVM Cloud connectVM Magnum](../kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-connectVM-Cloud-connectVM-Magnum.html.md)
|
||||
|
||||
### Performing administrative tasks within Windows based VMs[🔗](#performing-administrative-tasks-within-windows-based-vms "Permalink to this headline")
|
||||
|
||||
@ -1,16 +1,16 @@
|
||||
How to clone existing and configured VMs on 3Engines Cloud[🔗](#how-to-clone-existing-and-configured-vms-on-brand-name "Permalink to this headline")
|
||||
How to clone existing and configured VMs on connectVM 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 3Engines dashboard.
|
||||
The simplest way to create the snapshot of your machine is using “Horizon” - graphical interface of connectVM dashboard.
|
||||
|
||||
In summary, there will be 2 operations:
|
||||
|
||||
1. Creating snapshot
|
||||
2. Restoring snapshot to newly created VM.
|
||||
|
||||
To start, please visit our website <https://3engine.rootxwire.com/> and login.
|
||||
To start, please visit our website <https://console.connectvm.com/> and login.
|
||||
|
||||
|
||||
|
||||
|
||||
After logon, in **“Instances”** menu select VM to be cloned, and create its snapshot by clicking “Actions” Menu
|
||||
|
||||
@ -22,7 +22,7 @@ Once the snapshot is ready, you may see it on **“Images”** page of Horizon.
|
||||
|
||||
Now, you may click **“Launch”** in right upper corner of the window or just go back to **“Instances”** menu and launch new instance.
|
||||
|
||||
Full manual is here: [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md)
|
||||
Full manual is here: [How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud](How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md)
|
||||
|
||||
But if this process is familiar to you, there is only one difference. Chose as the source **“boot from snapshot”** instead of **“boot from image”** and select your snapshot from the list below. In next steps select parameters (flavour, size), at least the same as the original one. (“Launch instance” button will be unavailable until all necessary settings were completed).
|
||||
|
||||
@ -32,4 +32,4 @@ Caution
|
||||
|
||||
If the original machine had any additional volumes attached to it, they should also be cloned.
|
||||
|
||||
You may also want to read: [Volume snapshot inheritance and its consequences on 3Engines Cloud](../datavolume/Volume-snapshot-inheritance-and-its-consequences-on-3Engines-Cloud.html.md).
|
||||
You may also want to read: [Volume snapshot inheritance and its consequences on connectVM Cloud](../datavolume/Volume-snapshot-inheritance-and-its-consequences-on-connectVM-Cloud.html.md).
|
||||
@ -1,7 +1,7 @@
|
||||
How to create Windows VM on 3Engines Horizon and access it via web console on 3Engines Cloud[🔗](#how-to-create-windows-vm-on-3Engines-horizon-and-access-it-via-web-console-on-brand-name "Permalink to this headline")
|
||||
How to create Windows VM on connectVM Horizon and access it via web console on connectVM Cloud[🔗](#how-to-create-windows-vm-on-connectVM-horizon-and-access-it-via-web-console-on-brand-name "Permalink to this headline")
|
||||
===========================================================================================================================================================================================================================
|
||||
|
||||
This article provides a straightforward way of creating a functional Windows VM on 3Engines Cloud cloud, using the Horizon graphical interface.
|
||||
This article provides a straightforward way of creating a functional Windows VM on connectVM Cloud cloud, using the Horizon graphical interface.
|
||||
|
||||
The idea is to
|
||||
|
||||
@ -27,7 +27,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with access to the Horizon interface: <https://console.connectvm.com/>.
|
||||
|
||||
Step 1: Access the Launch Instance menu[🔗](#step-1-access-the-launch-instance-menu "Permalink to this headline")
|
||||
----------------------------------------------------------------------------------------------------------------
|
||||
@ -214,6 +214,6 @@ Follow the appropriate prompts to update your operating system.
|
||||
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 3Engines Cloud](../windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-3Engines-Cloud.html.md)
|
||||
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 connectVM Cloud](../windows/Connecting-to-a-Windows-VM-via-RDP-through-a-Linux-bastion-host-port-forwarding-on-connectVM-Cloud.html.md)
|
||||
|
||||
To learn more about security groups, you can check this article: [How to use Security Groups in Horizon on 3Engines Cloud](How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md)
|
||||
To learn more about security groups, you can check this article: [How to use Security Groups in Horizon on connectVM Cloud](How-to-use-Security-Groups-in-Horizon-on-connectVM-Cloud.html.md)
|
||||
@ -1,9 +1,9 @@
|
||||
How to create a Linux VM and access it from Linux command line on 3Engines Cloud[🔗](#how-to-create-a-linux-vm-and-access-it-from-linux-command-line-on-brand-name "Permalink to this headline")
|
||||
How to create a Linux VM and access it from Linux command line on connectVM 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 3Engines 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.
|
||||
Creating a virtual machine in a connectVM 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.
|
||||
|
||||
If you want to access Linux VM from a Windows based command line, follow this article instead: [How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md).
|
||||
If you want to access Linux VM from a Windows based command line, follow this article instead: [How to create a Linux VM and access it from Windows desktop on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md).
|
||||
|
||||
Note
|
||||
|
||||
@ -12,7 +12,7 @@ This article only covers the basics of creating a VM - it does not cover topics
|
||||
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------------
|
||||
|
||||
> * Creating a Linux virtual machine in 3Engines Cloud cloud using command **Launch Instance** from Horizon Dashboard
|
||||
> * Creating a Linux virtual machine in connectVM Cloud cloud using command **Launch Instance** from Horizon Dashboard
|
||||
|
||||
You will enter the following required data into that window:
|
||||
|
||||
@ -36,7 +36,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Hosting**
|
||||
|
||||
You need a 3Engines Cloud hosting account with Horizon interface <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with Horizon interface <https://console.connectvm.com/>.
|
||||
|
||||
No. 2 **Basic knowledge of Linux terminal**
|
||||
|
||||
@ -48,13 +48,13 @@ A Linux distribution running on your computer. This article was written for Ubun
|
||||
|
||||
No. 4 **SSH client installed and configured on your local Linux computer**
|
||||
|
||||
The SSH client must be installed and configured on your local Linux computer. Please see [Generating an SSH keypair in Linux on 3Engines Cloud](../networking/Generating-a-SSH-keypair-in-Linux-on-3Engines-Cloud.html.md).
|
||||
The SSH client must be installed and configured on your local Linux computer. Please see [Generating an SSH keypair in Linux on connectVM Cloud](../networking/Generating-a-SSH-keypair-in-Linux-on-connectVM-Cloud.html.md).
|
||||
|
||||
If you already have an SSH key pair and an SSH client configured, you should import your public key to the Horizon dashboard. The following article contains information how to do it: [How to import SSH public key to 3Engines Horizon on 3Engines Cloud](../networking/How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md).
|
||||
If you already have an SSH key pair and an SSH client configured, you should import your public key to the Horizon dashboard. The following article contains information how to do it: [How to import SSH public key to connectVM Horizon on connectVM Cloud](../networking/How-to-Import-SSH-Public-Key-to-connectVM-Horizon-on-connectVM-Cloud.html.md).
|
||||
|
||||
Alternatively, you can also create a key pair directly in the Horizon:
|
||||
|
||||
[How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md).
|
||||
[How to create key pair in connectVM Dashboard on connectVM Cloud](How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md).
|
||||
|
||||
Options for creation of a Virtual Machine (VM)[🔗](#options-for-creation-of-a-virtual-machine-vm "Permalink to this headline")
|
||||
-----------------------------------------------------------------------------------------------------------------------------
|
||||
@ -63,7 +63,7 @@ Creation of a virtual machine is divided into 11 sections, four of which are man
|
||||
|
||||
Note
|
||||
|
||||
In 3Engines terminology, a *virtual machine* is also an *instance*. *Instance* is a broader term as not all instances need be virtual machines, it is also possible to use real hardware as an instance.
|
||||
In connectVM terminology, a *virtual machine* is also an *instance*. *Instance* is a broader term as not all instances need be virtual machines, it is also possible to use real hardware as an instance.
|
||||
|
||||
The window to create a virtual machine is called **Launch Instance**. You will enter all the data about an instance into that window and its options.
|
||||
|
||||
@ -110,7 +110,7 @@ You should now see the following form:
|
||||
|
||||
|
||||
|
||||
The standard definition of 3Engines *flavor* is the amount of resources available to the instance - like VCPU, memory and storage capacity.
|
||||
The standard definition of connectVM *flavor* is the amount of resources available to the instance - like VCPU, memory and storage capacity.
|
||||
|
||||
Choose the one which suits you best and click **↑** next to it.
|
||||
|
||||
@ -130,7 +130,7 @@ To solve this issue, choose a flavor that supports your chosen source instead. I
|
||||
Another possible explanation might be that your quota is too low for creating a VM with your chosen flavor. You can see your quota in the **Compute -> Overview** section of your Horizon dashboard. If that is the case, you can either:
|
||||
|
||||
* choose a different flavor or
|
||||
* contact the 3Engines Cloud Support to request quota increase - [Helpdesk and Support](../accountmanagement/Help-Desk-And-Support.html.md).
|
||||
* contact the connectVM Cloud Support to request quota increase - [Helpdesk and Support](../accountmanagement/Help-Desk-And-Support.html.md).
|
||||
|
||||
Click **Next** or click **Networks** to define networks.
|
||||
|
||||
@ -178,7 +178,7 @@ In the image above, the key is called **test-key**. There are three ways to ente
|
||||
|
||||
> * using option **Create Key Pair** – create it on the spot,
|
||||
> * using option **Import Key Pair** – take the keys you already have and upload them to the cloud,
|
||||
> * using one of the key pairs that were already existing within 3Engines cloud.
|
||||
> * using one of the key pairs that were already existing within connectVM cloud.
|
||||
|
||||
If you haven’t created your key pair yet, please follow Prerequisite No. 4.
|
||||
|
||||
@ -208,7 +208,7 @@ Just like on the above screenshot, under header **IP Address**, you will see net
|
||||
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 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md).
|
||||
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 connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md).
|
||||
|
||||
Once you have added the floating IP, you will see it in the Horizon dashboard under header **IP Address** - just like in the last image from that article:
|
||||
|
||||
@ -219,7 +219,7 @@ The floating IP address in that article is **64.225.132.0**. Your address will v
|
||||
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 3Engines Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md).
|
||||
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 connectVM Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md).
|
||||
|
||||
The last command in that article was:
|
||||
|
||||
@ -233,7 +233,7 @@ The IP address in that article is **64.225.132.99** and is different from the ad
|
||||
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
|
||||
-----------------------------------------------------------------
|
||||
|
||||
3Engines Cloud cloud can be used for general hosting needs, such as
|
||||
connectVM Cloud cloud can be used for general hosting needs, such as
|
||||
|
||||
> * installing LAMP servers,
|
||||
> * installing and using WordPress servers,
|
||||
@ -242,20 +242,20 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
|
||||
|
||||
To create a *cluster* of instances, see the series of articles on Kubernetes:
|
||||
|
||||
[How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](../kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md).
|
||||
[How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](../kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md).
|
||||
|
||||
If you find yourself unable to connect to your virtual machine using SSH, you can use the web console for troubleshooting and other purposes. Here’s how to do it:
|
||||
|
||||
[How to access the VM from 3Engines console on 3Engines Cloud](How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md)
|
||||
[How to access the VM from connectVM console on connectVM Cloud](How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md)
|
||||
|
||||
If you don’t want the storage of your instance to be deleted while the VM is removed, you can choose to use a volume during instance creation. Please see the following articles:
|
||||
|
||||
[VM created with option Create New Volume No on 3Engines Cloud](VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md)
|
||||
[VM created with option Create New Volume No on connectVM Cloud](VM-created-with-option-Create-New-Volume-No-on-connectVM-Cloud.html.md)
|
||||
|
||||
[VM created with option Create New Volume Yes on 3Engines Cloud](VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md).
|
||||
[VM created with option Create New Volume Yes on connectVM Cloud](VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md).
|
||||
|
||||
You can’t apply the SSH keys uploaded to the Horizon dashboard directly to a VM after its creation. The following article presents a walkaround to this problem:
|
||||
|
||||
[How to add SSH key from Horizon web console on 3Engines Cloud](../networking/How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md).
|
||||
[How to add SSH key from Horizon web console on connectVM Cloud](../networking/How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md).
|
||||
|
||||
If you find that the storage of your VM is insufficient for your needs, you can attach the volume to it after its creation. The following articles contain appropriate instructions: [How to attach a volume to VM less than 2TB on Linux on 3Engines Cloud](../datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-3Engines-Cloud.html.md) and [How to attach a volume to VM more than 2TB on Linux on 3Engines Cloud](../datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-3Engines-Cloud.html.md).
|
||||
If you find that the storage of your VM is insufficient for your needs, you can attach the volume to it after its creation. The following articles contain appropriate instructions: [How to attach a volume to VM less than 2TB on Linux on connectVM Cloud](../datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-connectVM-Cloud.html.md) and [How to attach a volume to VM more than 2TB on Linux on connectVM Cloud](../datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-connectVM-Cloud.html.md).
|
||||
@ -1,9 +1,9 @@
|
||||
How to create a Linux VM and access it from Windows desktop on 3Engines Cloud[🔗](#how-to-create-a-linux-vm-and-access-it-from-windows-desktop-on-brand-name "Permalink to this headline")
|
||||
How to create a Linux VM and access it from Windows desktop on connectVM 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 3Engines 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.
|
||||
Creating a virtual machine in a connectVM 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.
|
||||
|
||||
If you want to access Linux VM from a Linux command line, follow this article instead: [How to create a Linux VM and access it from Linux command line on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md).
|
||||
If you want to access Linux VM from a Linux command line, follow this article instead: [How to create a Linux VM and access it from Linux command line on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md).
|
||||
|
||||
Note
|
||||
|
||||
@ -12,7 +12,7 @@ This article only covers the basics of creating a VM - it does not cover topics
|
||||
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------------
|
||||
|
||||
> * Creating a Linux virtual machine in 3Engines Cloud cloud using command **Launch Instance** from Horizon Dashboard
|
||||
> * Creating a Linux virtual machine in connectVM Cloud cloud using command **Launch Instance** from Horizon Dashboard
|
||||
|
||||
You will enter the following data into that window:
|
||||
|
||||
@ -42,7 +42,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Hosting**
|
||||
|
||||
You need a 3Engines Cloud hosting account with Horizon interface <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with Horizon interface <https://console.connectvm.com/>.
|
||||
|
||||
No. 2 **Basic knowledge of Linux terminal**
|
||||
|
||||
@ -60,9 +60,9 @@ No. 5 **SSH key**
|
||||
|
||||
You need to have an SSH key pair. It consists of a public and private key. You can use your existing pair in this workflow or create a new one. If you do not have one, you have several options, such as:
|
||||
|
||||
* Generate them directly using the Horizon dashboard: [How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md).
|
||||
* Generate them directly using the Horizon dashboard: [How to create key pair in connectVM Dashboard on connectVM Cloud](How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md).
|
||||
|
||||
* Generate your key pair using the Windows command line. Please check this article: [How to Create SSH Key Pair in Windows 10 On 3Engines Cloud](../windows/How-To-Create-SSH-Key-Pair-In-Windows-On-3Engines-Cloud.html.md). If you choose that option, make sure that you upload your public key to the Horizon dashboard: [How to import SSH public key to 3Engines Horizon on 3Engines Cloud](../networking/How-to-Import-SSH-Public-Key-to-3Engines-Horizon-on-3Engines-Cloud.html.md).
|
||||
* Generate your key pair using the Windows command line. Please check this article: [How to Create SSH Key Pair in Windows 10 On connectVM Cloud](../windows/How-To-Create-SSH-Key-Pair-In-Windows-On-connectVM-Cloud.html.md). If you choose that option, make sure that you upload your public key to the Horizon dashboard: [How to import SSH public key to connectVM Horizon on connectVM Cloud](../networking/How-to-Import-SSH-Public-Key-to-connectVM-Horizon-on-connectVM-Cloud.html.md).
|
||||
|
||||
This article contains information about configuring PuTTY using one such key pair.
|
||||
|
||||
@ -73,7 +73,7 @@ Creation of a virtual machine is divided into 11 sections, four of which are man
|
||||
|
||||
Note
|
||||
|
||||
In 3Engines terminology, a *virtual machine* is also an *instance*. *Instance* is a broader term as not all instances need be virtual machines, it is also possible to use real hardware as an instance.
|
||||
In connectVM terminology, a *virtual machine* is also an *instance*. *Instance* is a broader term as not all instances need be virtual machines, it is also possible to use real hardware as an instance.
|
||||
|
||||
The window to create a virtual machine is called **Launch Instance**. You will enter all the data about an instance into that window.
|
||||
|
||||
@ -120,7 +120,7 @@ You should now see the following form:
|
||||
|
||||
|
||||
|
||||
The standard definition of 3Engines *flavor* is the amount of resources available to the instance - like VCPU, memory and storage capacity.
|
||||
The standard definition of connectVM *flavor* is the amount of resources available to the instance - like VCPU, memory and storage capacity.
|
||||
|
||||
Choose the one which suits you best and click **↑** next to it.
|
||||
|
||||
@ -142,7 +142,7 @@ To solve this issue, choose a flavor that supports your chosen source instead. I
|
||||
Another possible cause might be that your quota is too low for creating a VM with your chosen flavor. You can see your quota in the **Compute -> Overview** section of your Horizon dashboard. If that is the case, you can either:
|
||||
|
||||
* choose a different flavor or
|
||||
* contact the 3Engines Cloud Support to request quota increase - [Helpdesk and Support](../accountmanagement/Help-Desk-And-Support.html.md).
|
||||
* contact the connectVM Cloud Support to request quota increase - [Helpdesk and Support](../accountmanagement/Help-Desk-And-Support.html.md).
|
||||
|
||||
Click **Next** or click **Networks** to define networks.
|
||||
|
||||
@ -193,7 +193,7 @@ In the image above, the key is called **test-key**. There are three ways to ente
|
||||
|
||||
> * using option **Create Key Pair** – create it on the spot,
|
||||
> * using option **Import Key Pair** – take the keys you already have and upload them to the cloud,
|
||||
> * using one of the key pairs that were already existing within 3Engines cloud.
|
||||
> * using one of the key pairs that were already existing within connectVM cloud.
|
||||
|
||||
If you haven’t created your key pair yet, please follow Prerequisite No. 5.
|
||||
|
||||
@ -223,7 +223,7 @@ Just like on the above screenshot, under header **IP Address**, you will see net
|
||||
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 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md).
|
||||
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 connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md).
|
||||
|
||||
Once you have added the floating IP, you will see it in the Horizon dashboard under header **IP Address** - just like in the last image from that article:
|
||||
|
||||
@ -325,7 +325,7 @@ Type **eouser** and press Enter.
|
||||
|
||||
Note
|
||||
|
||||
User **eouser** is the predefined Linux user name on default images on 3Engines Cloud hosting.
|
||||
User **eouser** is the predefined Linux user name on default images on connectVM Cloud hosting.
|
||||
|
||||
You should now be connected to your virtual machine and be able to execute commands:
|
||||
|
||||
@ -345,7 +345,7 @@ You can now start your session as explained in Step 12 above.
|
||||
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
|
||||
-----------------------------------------------------------------
|
||||
|
||||
3Engines Cloud cloud can be used for general hosting needs, such as
|
||||
connectVM Cloud cloud can be used for general hosting needs, such as
|
||||
|
||||
> * installing LAMP servers,
|
||||
> * installing and using WordPress servers,
|
||||
@ -354,20 +354,20 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
|
||||
|
||||
To create a *cluster* of instances, see the series of articles on Kubernetes:
|
||||
|
||||
[How to Create a Kubernetes Cluster Using 3Engines Cloud 3Engines Magnum](../kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-3Engines-Cloud-3Engines-Magnum.html.md).
|
||||
[How to Create a Kubernetes Cluster Using connectVM Cloud connectVM Magnum](../kubernetes/How-to-Create-a-Kubernetes-Cluster-Using-connectVM-Cloud-connectVM-Magnum.html.md).
|
||||
|
||||
If you find yourself unable to connect to your virtual machine using SSH, you can use the web console for troubleshooting and other purposes. Here’s how to do it:
|
||||
|
||||
[How to access the VM from 3Engines console on 3Engines Cloud](How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md)
|
||||
[How to access the VM from connectVM console on connectVM Cloud](How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md)
|
||||
|
||||
If you don’t want the storage of your instance to be deleted while the VM is removed, you can choose to use a volume during instance creation. Please see the following articles:
|
||||
|
||||
[VM created with option Create New Volume No on 3Engines Cloud](VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md)
|
||||
[VM created with option Create New Volume No on connectVM Cloud](VM-created-with-option-Create-New-Volume-No-on-connectVM-Cloud.html.md)
|
||||
|
||||
[VM created with option Create New Volume Yes on 3Engines Cloud](VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md).
|
||||
[VM created with option Create New Volume Yes on connectVM Cloud](VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md).
|
||||
|
||||
You can’t apply the SSH keys uploaded to the Horizon dashboard directly to a VM after its creation. The following article presents a walkaround to this problem:
|
||||
|
||||
[How to add SSH key from Horizon web console on 3Engines Cloud](../networking/How-to-add-SSH-key-from-Horizon-web-console-on-3Engines-Cloud.html.md).
|
||||
[How to add SSH key from Horizon web console on connectVM Cloud](../networking/How-to-add-SSH-key-from-Horizon-web-console-on-connectVM-Cloud.html.md).
|
||||
|
||||
If you find that the storage of your VM is insufficient for your needs, you can attach the volume to it after its creation. The following articles contain appropriate instructions: [How to attach a volume to VM less than 2TB on Linux on 3Engines Cloud](../datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-3Engines-Cloud.html.md) and [How to attach a volume to VM more than 2TB on Linux on 3Engines Cloud](../datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-3Engines-Cloud.html.md).
|
||||
If you find that the storage of your VM is insufficient for your needs, you can attach the volume to it after its creation. The following articles contain appropriate instructions: [How to attach a volume to VM less than 2TB on Linux on connectVM Cloud](../datavolume/How-to-attach-a-volume-to-VM-less-than-2TB-on-Linux-on-connectVM-Cloud.html.md) and [How to attach a volume to VM more than 2TB on Linux on connectVM Cloud](../datavolume/How-to-attach-a-volume-to-VM-more-than-2TB-on-Linux-on-connectVM-Cloud.html.md).
|
||||
@ -1,12 +1,12 @@
|
||||
How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud[🔗](#how-to-create-a-vm-using-the-3Engines-cli-client-on-brand-name-cloud "Permalink to this headline")
|
||||
How to create a VM using the connectVM CLI client on connectVM Cloud cloud[🔗](#how-to-create-a-vm-using-the-connectVM-cli-client-on-brand-name-cloud "Permalink to this headline")
|
||||
===================================================================================================================================================================================
|
||||
|
||||
This article will cover creating a virtual machine on 3Engines Cloud cloud using the 3Engines CLI client exclusively. It contains basic information to get you started.
|
||||
This article will cover creating a virtual machine on connectVM Cloud cloud using the connectVM CLI client exclusively. It contains basic information to get you started.
|
||||
|
||||
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------------
|
||||
|
||||
> * The **3Engines** command to create a VM
|
||||
> * The **connectVM** command to create a VM
|
||||
> * Selecting parameters of the new virtual machine
|
||||
>
|
||||
> > * Image
|
||||
@ -24,20 +24,20 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with access to the Horizon interface: <https://console.connectvm.com/>.
|
||||
|
||||
No. 2 **3Engines CLI client configured**
|
||||
No. 2 **connectVM CLI client configured**
|
||||
|
||||
To have the 3Engines CLI client configured and operational, see article: [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md).
|
||||
To have the connectVM CLI client configured and operational, see article: [How to install connectVMClient for Linux on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md).
|
||||
|
||||
If the command
|
||||
|
||||
```
|
||||
3Engines flavor list
|
||||
connectVM flavor list
|
||||
|
||||
```
|
||||
|
||||
shows a list of flavors, the **3Engines** command is operational.
|
||||
shows a list of flavors, the **connectVM** command is operational.
|
||||
|
||||
No. 3 **Available image to create a new VM from**
|
||||
|
||||
@ -50,18 +50,18 @@ In general, you can create a new virtual machine from these four sources:
|
||||
|
||||
In this article, we will use the first option, an operating system image, as a source of a new virtual machine. There are three ways you can obtain an image:
|
||||
|
||||
Images that are automatically included on 3Engines Cloud cloud
|
||||
Images that are automatically included on connectVM Cloud cloud
|
||||
: There is a set of images that come predefined with the cloud. Typically, that default list of images will contain Ubuntu, CentOS, and Windows 2019/22 images, with various flavors. Other default images could be available as well, say, for AlmaLinux, OPNSense, OSGeolive, Rocky Linux and so on.
|
||||
|
||||
Images shared from other projects
|
||||
: Under 3Engines, images can be shared between the projects. To have an alien image available in your project, you have to accept it first.
|
||||
: Under connectVM, images can be shared between the projects. To have an alien image available in your project, you have to accept it first.
|
||||
|
||||
Images uploaded within your account
|
||||
: Finally, you can upload an image by yourself. Once uploaded, the image will be a first class citizen but it may not be automatically available on other accounts you might have.
|
||||
|
||||
See this article
|
||||
|
||||
[How to upload your custom image using 3Engines CLI on 3Engines Cloud](How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md)
|
||||
[How to upload your custom image using connectVM CLI on connectVM Cloud](How-to-upload-your-custom-image-using-connectVM-CLI-on-connectVM-Cloud.html.md)
|
||||
|
||||
for an example of uploading a new Debian image to the cloud.
|
||||
|
||||
@ -69,4 +69,4 @@ No. 4 **Available SSH key pair**
|
||||
|
||||
These two articles should help generate and import the SSH key into the cloud:
|
||||
|
||||
* /networking/Generating-a-sshkeypair-in-Linux-on-3Engines-Cloud and
|
||||
* /networking/Generating-a-sshkeypair-in-Linux-on-connectVM-Cloud and
|
||||
@ -1,7 +1,7 @@
|
||||
How to create instance snapshot using Horizon on 3Engines Cloud[🔗](#how-to-create-instance-snapshot-using-horizon-on-brand-name "Permalink to this headline")
|
||||
How to create instance snapshot using Horizon on connectVM 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 3Engines Cloud cloud, using Horizon dashboard.
|
||||
In this article, you will learn how to create instance snapshot on connectVM Cloud cloud, using Horizon dashboard.
|
||||
|
||||
Instance snapshots allow you to archive the state of the virtual machine. You can, then, use them for
|
||||
|
||||
@ -49,14 +49,14 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with access to the Horizon interface: <https://console.connectvm.com/>.
|
||||
|
||||
No. 2 **Ephemeral storage vs. persistent storage**
|
||||
|
||||
Please see article [Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in 3Engines.
|
||||
Please see article [Ephemeral vs Persistent storage option Create New Volume on connectVM Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-connectVM-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in connectVM.
|
||||
|
||||
No. 3 **Instance with ephemeral storage**
|
||||
|
||||
You need a virtual machine hosted on 3Engines Cloud cloud.
|
||||
You need a virtual machine hosted on connectVM Cloud cloud.
|
||||
|
||||
Using any of the following articles will produce an instance with ephemeral storage:
|
||||
@ -1,4 +1,4 @@
|
||||
How to create key pair in 3Engines Dashboard on 3Engines Cloud[🔗](#how-to-create-key-pair-in-3Engines-dashboard-on-brand-name "Permalink to this headline")
|
||||
How to create key pair in connectVM Dashboard on connectVM Cloud[🔗](#how-to-create-key-pair-in-connectVM-dashboard-on-brand-name "Permalink to this headline")
|
||||
===============================================================================================================================================================
|
||||
|
||||
Open **Compute -> Key Pairs**
|
||||
@ -30,8 +30,8 @@ Click key name in **Key Pairs** menu and read your **public key**. You can also
|
||||
|
||||
* To connect via SSH to your Virtual Machine using Linux, follow the steps in this FAQ:
|
||||
|
||||
[How to connect to your virtual machine via SSH in Linux on 3Engines Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-3Engines-Cloud.html.md)
|
||||
[How to connect to your virtual machine via SSH in Linux on connectVM Cloud](../networking/How-to-connect-to-your-virtual-machine-via-SSH-in-Linux-on-connectVM-Cloud.html.md)
|
||||
|
||||
* To connect via SSH to your Virtual Machine using Windows (Command Prompt), follow the steps in this FAQ:
|
||||
|
||||
[How to connect to a virtual machine via SSH from Windows 10 Command Prompt on 3Engines Cloud](../windows/How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-3Engines-Cloud.html.md)
|
||||
[How to connect to a virtual machine via SSH from Windows 10 Command Prompt on connectVM Cloud](../windows/How-to-connect-to-a-virtual-machine-via-SSH-from-Windows-10-Command-Prompt-on-connectVM-Cloud.html.md)
|
||||
@ -1,4 +1,4 @@
|
||||
How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud[🔗](#how-to-create-new-linux-vm-in-3Engines-dashboard-horizon-on-brand-name "Permalink to this headline")
|
||||
How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud[🔗](#how-to-create-new-linux-vm-in-connectVM-dashboard-horizon-on-brand-name "Permalink to this headline")
|
||||
=======================================================================================================================================================================================
|
||||
|
||||
Go to **Project → Compute → Instances**.
|
||||
@ -31,7 +31,7 @@ Open **“Security Groups”** After that, choose “default” and “allow\_pi
|
||||
|
||||
|
||||
|
||||
Choose or generate SSH keypair [How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md) for your VM. Next, launch your instance by clicking on blue button.
|
||||
Choose or generate SSH keypair [How to create key pair in connectVM Dashboard on connectVM Cloud](How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md) for your VM. Next, launch your instance by clicking on blue button.
|
||||
|
||||
|
||||
|
||||
@ -61,4 +61,4 @@ After you finish, type “exit”.
|
||||
|
||||
This will close the session.
|
||||
|
||||
If you want to make your VM accessible from the Internet check [How to Add or Remove Floating IP’s to your VM on 3Engines Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-3Engines-Cloud.html.md).
|
||||
If you want to make your VM accessible from the Internet check [How to Add or Remove Floating IP’s to your VM on connectVM Cloud](../networking/How-to-Add-or-Remove-Floating-IPs-to-your-VM-on-connectVM-Cloud.html.md).
|
||||
@ -1,9 +1,9 @@
|
||||
How to fix unresponsive console issue on 3Engines Cloud[🔗](#how-to-fix-unresponsive-console-issue-on-brand-name "Permalink to this headline")
|
||||
How to fix unresponsive console issue on connectVM 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.
|
||||
|
||||
After opening up the console in 3Engines you might encounter this error:
|
||||
After opening up the console in connectVM you might encounter this error:
|
||||
|
||||
* unresponsive grey screen
|
||||
* document icon in the down-right corner which informs about the issue on client side
|
||||
@ -1,24 +0,0 @@
|
||||
How to generate and manage EC2 credentials on 3Engines 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 3Engines 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
|
||||
|
||||
> * on your virtual machines and
|
||||
> * on your local computers.
|
||||
|
||||
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")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Hosting**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to Horizon interface: <https://3engine.rootxwire.com/>
|
||||
|
||||
No. 2 **3Engines CLI client installed and configured**
|
||||
|
||||
You need to have the 3Engines CLI operational.
|
||||
|
||||
First, it must be installed. You have several options, such as:
|
||||
@ -0,0 +1,24 @@
|
||||
How to generate and manage EC2 credentials on connectVM 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 connectVM 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
|
||||
|
||||
> * on your virtual machines and
|
||||
> * on your local computers.
|
||||
|
||||
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")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Hosting**
|
||||
|
||||
You need a connectVM Cloud hosting account with access to Horizon interface: <https://console.connectvm.com/>
|
||||
|
||||
No. 2 **connectVM CLI client installed and configured**
|
||||
|
||||
You need to have the connectVM CLI operational.
|
||||
|
||||
First, it must be installed. You have several options, such as:
|
||||
@ -1,4 +1,4 @@
|
||||
How to generate or use Application Credentials via CLI on 3Engines 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 connectVM 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.
|
||||
@ -10,24 +10,24 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Hosting**
|
||||
|
||||
You need a 3Engines Cloud hosting account with Horizon interface <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with Horizon interface <https://console.connectvm.com/>.
|
||||
|
||||
No. 2 **Authenticate**
|
||||
|
||||
Once you have installed this piece of software, you need to authenticate to start using it: [How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md)
|
||||
Once you have installed this piece of software, you need to authenticate to start using it: [How to activate connectVM CLI access to connectVM Cloud cloud using one- or two-factor authentication](../accountmanagement/How-to-activate-connectVM-CLI-access-to-connectVM-Cloud-cloud-using-one-or-two-factor-authentication.html.md)
|
||||
|
||||
No. 3 **3EnginesClient installed and available**
|
||||
No. 3 **connectVMClient installed and available**
|
||||
|
||||
3Engines is written in Python, it is recommended to use a dedicated virtual environment for the rest of this article.
|
||||
connectVM is written in Python, it is recommended to use a dedicated virtual environment for the rest of this article.
|
||||
|
||||
Install GitBash on Windows
|
||||
: [How to install 3EnginesClient GitBash for Windows on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md).
|
||||
: [How to install connectVMClient GitBash for Windows on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-GitBash-or-Cygwin-for-Windows-on-connectVM-Cloud.html.md).
|
||||
|
||||
Install and run WSL (Linux under Windows)
|
||||
: [How to install 3EnginesClient on Windows using Windows Subsystem for Linux on 3Engines Cloud 3Engines Hosting](../3Enginescli/How-to-install-3EnginesClient-on-Windows-using-Windows-Subsystem-for-Linux-on-3Engines-Cloud-3Engines-Hosting.html.md).
|
||||
: [How to install connectVMClient on Windows using Windows Subsystem for Linux on connectVM Cloud connectVM Hosting](../connectVMcli/How-to-install-connectVMClient-on-Windows-using-Windows-Subsystem-for-Linux-on-connectVM-Cloud-connectVM-Hosting.html.md).
|
||||
|
||||
Install 3EnginesClient on Linux
|
||||
: [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md).
|
||||
Install connectVMClient on Linux
|
||||
: [How to install connectVMClient for Linux on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md).
|
||||
|
||||
No. 4 **jq installed and running**
|
||||
|
||||
@ -46,7 +46,7 @@ Step 1 CLI Commands for Application Credentials[🔗](#step-1-cli-commands-for-a
|
||||
Command
|
||||
|
||||
```
|
||||
3Engines application credential
|
||||
connectVM application credential
|
||||
|
||||
```
|
||||
|
||||
@ -63,7 +63,7 @@ application credential show
|
||||
To see the parameters for these commands, end them with **--help**, like this:
|
||||
|
||||
```
|
||||
3Engines application credential create --help
|
||||
connectVM application credential create --help
|
||||
|
||||
```
|
||||
|
||||
@ -81,7 +81,7 @@ Step 2 The Simplest Way to Create a New Application Credential[🔗](#step-2-the
|
||||
The simplest way to generate a new application credential is just to define the name – the rest of the parameters will be defined automatically for you. The following command uses name **cred2**:
|
||||
|
||||
```
|
||||
3Engines application credential create cred2
|
||||
connectVM application credential create cred2
|
||||
|
||||
```
|
||||
|
||||
@ -109,7 +109,7 @@ _member_ magnum_user load-balancer_member heat_stack_owner creator k8s_admin
|
||||
|
||||
Note
|
||||
|
||||
Role **\_member\_** is the most basic role and should always be present. Beware however, as in some variations of 3Engines it can be called **member** instead of **\_member\_**.
|
||||
Role **\_member\_** is the most basic role and should always be present. Beware however, as in some variations of connectVM it can be called **member** instead of **\_member\_**.
|
||||
|
||||
**--expiration**
|
||||
|
||||
@ -134,7 +134,7 @@ By default, for security reasons, application credentials are forbidden from bei
|
||||
Here is a complete example, using all of the available parameters to create a new application credential:
|
||||
|
||||
```
|
||||
3Engines application credential create foo-dev-member4 --role _member_ --expiration $(date +"%Y-11-%dT%H:%M:%S") --description "Test application credentials" --unrestricted -c id -c secret -f json | jq -r '"application_credential_id: \"" + .id + "\"", "application_credential_secret: \"" + .secret + "\""'
|
||||
connectVM application credential create foo-dev-member4 --role _member_ --expiration $(date +"%Y-11-%dT%H:%M:%S") --description "Test application credentials" --unrestricted -c id -c secret -f json | jq -r '"application_credential_id: \"" + .id + "\"", "application_credential_secret: \"" + .secret + "\""'
|
||||
|
||||
```
|
||||
|
||||
@ -147,7 +147,7 @@ The name of the new application credential will be **foo-dev-member4**, will be
|
||||
Step 4 Enter id and secret into clouds.yml[🔗](#step-4-enter-id-and-secret-into-clouds-yml "Permalink to this headline")
|
||||
-----------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
You are now going to store the values of **id** and **secret** that the cloud has sent to you. Once stored, future **3Engines** commands will use these value to authenticate to the cloud without using any kind of password.
|
||||
You are now going to store the values of **id** and **secret** that the cloud has sent to you. Once stored, future **connectVM** commands will use these value to authenticate to the cloud without using any kind of password.
|
||||
|
||||
The place to store *id* and *secret* is a file called *clouds.yml*. It may reside on your local computer in one of these three locations:
|
||||
|
||||
@ -159,14 +159,14 @@ Current directory
|
||||
The current directory is searched first.
|
||||
|
||||
User configuration directory
|
||||
: **$HOME/.config/3Engines/clouds.yml**
|
||||
: **$HOME/.config/connectVM/clouds.yml**
|
||||
|
||||
The most common default location for individual users.
|
||||
|
||||
Searched after the current directory.
|
||||
|
||||
System-wide configuration directory
|
||||
: **/etc/3Engines/clouds.yml**
|
||||
: **/etc/connectVM/clouds.yml**
|
||||
|
||||
Searches that location as the last resort.
|
||||
|
||||
@ -181,7 +181,7 @@ The contents of the *clouds.yml* file will be in *yaml* format. It is customary
|
||||
Let us create a new application credential called *trial-member\_creatornew*.
|
||||
|
||||
```
|
||||
3Engines application credential create trial-member_creatornew --unrestricted -c id -c secret -f json | jq -r '"application_credential_id: \"" + .id + "\"", "application_credential_secret: \"" + .secret + "\""'
|
||||
connectVM application credential create trial-member_creatornew --unrestricted -c id -c secret -f json | jq -r '"application_credential_id: \"" + .id + "\"", "application_credential_secret: \"" + .secret + "\""'
|
||||
|
||||
```
|
||||
|
||||
@ -192,7 +192,7 @@ This is the result:
|
||||
Now create the *clouds.yml* file using your preferred editor of choice. Here it is *nano*:
|
||||
|
||||
```
|
||||
nano $HOME/.config/3Engines/clouds.yml
|
||||
nano $HOME/.config/connectVM/clouds.yml
|
||||
|
||||
```
|
||||
|
||||
@ -205,7 +205,7 @@ clouds:
|
||||
trial-member_creatornew:
|
||||
auth_type: "v3applicationcredential"
|
||||
auth:
|
||||
auth_url: https://keystone.3Engines.com:5000/v3
|
||||
auth_url: https://keystone.connectVM.com:5000/v3
|
||||
application_credential_id: "a582edb593644106baeaa75fd706feb2"
|
||||
application_credential_secret: "mPKQort71xi7Ros7BHb1sG4753wvN_tmJMBd1aRBBGzgFZM7AoUkLWzCutQuh-dAyac86-rkikYqqYaT1_f0hA"
|
||||
|
||||
@ -217,7 +217,7 @@ Let us dissect that file line by line:
|
||||
> * **trial-member\_creatornew** is the name of the application credential used in the previous *credential create* command.
|
||||
> * **v3applicationcredential** is the type of auth connection (it is always the same)
|
||||
> * **auth** start of *auth* parameters
|
||||
> * **auth\_url** the address to call on the 3Engines Cloud 3Engines server (it always the same)
|
||||
> * **auth\_url** the address to call on the connectVM Cloud connectVM server (it always the same)
|
||||
> * **application\_credential\_id** the value from the previous call of *credential create* command
|
||||
> * **credential create** command the value from the previous call of *credential create* command
|
||||
|
||||
@ -254,7 +254,7 @@ It works.
|
||||
You can also use that parameter in the command line, like this:
|
||||
|
||||
```
|
||||
3Engines --os-cloud=trial-member_creatornew flavor list
|
||||
connectVM --os-cloud=trial-member_creatornew flavor list
|
||||
|
||||
```
|
||||
|
||||
@ -262,7 +262,7 @@ It works as well:
|
||||
|
||||
|
||||
|
||||
You have to set up **OS\_CLOUD** once per opening a new terminal window and then you can use **3Engines** command without interpolating **--os-cloud** parameter all the time.
|
||||
You have to set up **OS\_CLOUD** once per opening a new terminal window and then you can use **connectVM** command without interpolating **--os-cloud** parameter all the time.
|
||||
|
||||
If you had two or more clouds defined in the *clouds.yml* file, then using **--os-cloud** in the command line would be more flexible.
|
||||
|
||||
@ -299,8 +299,8 @@ What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
|
||||
|
||||
Here are some articles that use application credentials:
|
||||
|
||||
[How to install Rancher RKE2 Kubernetes on 3Engines Cloud](../kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-3Engines-Cloud-cloud.html.md)
|
||||
[How to install Rancher RKE2 Kubernetes on connectVM Cloud](../kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-connectVM-Cloud-cloud.html.md)
|
||||
|
||||
[Configuring IP Whitelisting for 3Engines Load Balancer using Terraform on 3Engines Cloud](../kubernetes/Configuring-IP-Whitelisting-for-3Engines-Load-Balancer-using-Terraform-on-3Engines-Cloud.html.md)
|
||||
[Configuring IP Whitelisting for connectVM Load Balancer using Terraform on connectVM Cloud](../kubernetes/Configuring-IP-Whitelisting-for-connectVM-Load-Balancer-using-Terraform-on-connectVM-Cloud.html.md)
|
||||
|
||||
[3Engines User Roles on 3Engines Cloud](3Engines-user-roles-on-3Engines-Cloud.html.md)
|
||||
[connectVM User Roles on connectVM Cloud](connectVM-user-roles-on-connectVM-Cloud.html.md)
|
||||
@ -1,4 +1,4 @@
|
||||
How to install Python virtualenv or virtualenvwrapper on 3Engines Cloud[🔗](#how-to-install-python-virtualenv-or-virtualenvwrapper-on-brand-name "Permalink to this headline")
|
||||
How to install Python virtualenv or virtualenvwrapper on connectVM 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.
|
||||
@ -1,4 +1,4 @@
|
||||
How to start a VM from a snapshot on 3Engines 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 connectVM 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")
|
||||
@ -32,7 +32,7 @@ a) Volume Snapshot[🔗](#a-volume-snapshot "Permalink to this headline")
|
||||
|
||||
|
||||
|
||||
8. The rest of procedure is the same: [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md).
|
||||
8. The rest of procedure is the same: [How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud](How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md).
|
||||
|
||||
9. Newly created machine is visible in the Instances list.
|
||||
|
||||
@ -66,7 +66,7 @@ In the “Images” you may also find symbolic links to the volume snapshots.(i.
|
||||
|
||||
|
||||
|
||||
6. The rest of procedure is the same: [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md).
|
||||
6. The rest of procedure is the same: [How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud](How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md).
|
||||
|
||||
7. Virtual machine has been created.
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
How to start a VM from instance snapshot using Horizon dashboard on 3Engines Cloud[🔗](#how-to-start-a-vm-from-instance-snapshot-using-horizon-dashboard-on-brand-name "Permalink to this headline")
|
||||
How to start a VM from instance snapshot using Horizon dashboard on connectVM 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.
|
||||
@ -8,11 +8,11 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with access to the Horizon interface: <https://console.connectvm.com/>.
|
||||
|
||||
No. 2 **Ephemeral storage vs. persistent storage**
|
||||
|
||||
Please see article [Ephemeral vs Persistent storage option Create New Volume on 3Engines Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-3Engines-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in 3Engines.
|
||||
Please see article [Ephemeral vs Persistent storage option Create New Volume on connectVM Cloud](../datavolume/Ephemeral-vs-Persistent-storage-option-Create-New-Volume-on-connectVM-Cloud.html.md) to understand the basic difference between ephemeral and persistent types of storage in connectVM.
|
||||
|
||||
No. 3 **Instance snapshot**
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
How to transfer volumes between domains and projects using Horizon dashboard on 3Engines Cloud[🔗](#how-to-transfer-volumes-between-domains-and-projects-using-horizon-dashboard-on-brand-name "Permalink to this headline")
|
||||
How to transfer volumes between domains and projects using Horizon dashboard on connectVM Cloud[🔗](#how-to-transfer-volumes-between-domains-and-projects-using-horizon-dashboard-on-brand-name "Permalink to this headline")
|
||||
=============================================================================================================================================================================================================================
|
||||
|
||||
Volumes in 3Engines can be used to store data. They are visible to virtual machines like drives.
|
||||
Volumes in connectVM can be used to store data. They are visible to virtual machines like drives.
|
||||
|
||||
Such a volume is usually available to just the project in which it was created. Transferring data stored on it between projects might take a long time, especially if such a volume contains lots of data, like, say, hundreds or thousands of gigabytes (or even more).
|
||||
|
||||
@ -21,7 +21,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://3engine.rootxwire.com/>
|
||||
You need a connectVM Cloud hosting account with access to the Horizon interface: <https://console.connectvm.com/>
|
||||
|
||||
No. 2 **Volume**
|
||||
|
||||
@ -33,7 +33,7 @@ You can check the status of your volume in the **Volumes -> Volumes** section of
|
||||
|
||||
|
||||
|
||||
The following article includes information how to disconnect a volume from a virtual machine: [How to move data volume between two VMs using 3Engines Horizon on 3Engines Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-3Engines-Horizon-on-3Engines-Cloud.html.md)
|
||||
The following article includes information how to disconnect a volume from a virtual machine: [How to move data volume between two VMs using connectVM Horizon on connectVM Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-connectVM-Horizon-on-connectVM-Cloud.html.md)
|
||||
|
||||
No. 4 **Ability to perform operations on both the source project and the destination project**
|
||||
|
||||
@ -141,6 +141,6 @@ After cancelling, your volume should now once again have status **Available**:
|
||||
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
|
||||
-----------------------------------------------------------------
|
||||
|
||||
Now that the volume has been transferred, you might want to connect it to a virtual machine. This article includes information how to do that: [How to move data volume between two VMs using 3Engines Horizon on 3Engines Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-3Engines-Horizon-on-3Engines-Cloud.html.md)
|
||||
Now that the volume has been transferred, you might want to connect it to a virtual machine. This article includes information how to do that: [How to move data volume between two VMs using connectVM Horizon on connectVM Cloud](../datavolume/How-to-move-data-volume-between-two-VMs-using-connectVM-Horizon-on-connectVM-Cloud.html.md)
|
||||
|
||||
The workflow described in this article can also be done using the 3Engines CLI. Learn more here: [How to transfer volumes between domains and projects using 3Engines CLI client on 3Engines Cloud](../3Enginescli/How-to-transfer-volumes-between-domains-and-projects-using-3Engines-CLI-client-on-3Engines-Cloud.html.md)
|
||||
The workflow described in this article can also be done using the connectVM CLI. Learn more here: [How to transfer volumes between domains and projects using connectVM CLI client on connectVM Cloud](../connectVMcli/How-to-transfer-volumes-between-domains-and-projects-using-connectVM-CLI-client-on-connectVM-Cloud.html.md)
|
||||
@ -1,12 +1,12 @@
|
||||
How to upload custom image to 3Engines Cloud cloud using 3Engines Horizon dashboard[🔗](#how-to-upload-custom-image-to-brand-name-cloud-using-3Engines-horizon-dashboard "Permalink to this headline")
|
||||
How to upload custom image to connectVM Cloud cloud using connectVM Horizon dashboard[🔗](#how-to-upload-custom-image-to-brand-name-cloud-using-connectVM-horizon-dashboard "Permalink to this headline")
|
||||
=========================================================================================================================================================================================================
|
||||
|
||||
In this tutorial, you will upload custom image stored on your local computer to 3Engines Cloud cloud, using the Horizon Dashboard. The uploaded image will be available within your project alongside default images from 3Engines Cloud cloud and you will be able to create virtual machines using it.
|
||||
In this tutorial, you will upload custom image stored on your local computer to connectVM Cloud cloud, using the Horizon Dashboard. The uploaded image will be available within your project alongside default images from connectVM Cloud cloud and you will be able to create virtual machines using it.
|
||||
|
||||
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------------
|
||||
|
||||
> * How to check for the presence of image in 3Engines Cloud cloud
|
||||
> * How to check for the presence of image in connectVM Cloud cloud
|
||||
> * How different images might behave
|
||||
> * How to upload an image using Horizon dashboard
|
||||
> * Example: how to upload image for Debian 11
|
||||
@ -17,7 +17,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with access to the Horizon interface: <https://console.connectvm.com/>.
|
||||
|
||||
No. 2 **Custom image you wish to upload**
|
||||
|
||||
@ -35,8 +35,8 @@ The following container formats are supported:
|
||||
> | aki | ami | ari | bare |
|
||||
> | docker | ova | ovf | |
|
||||
|
||||
For the explanation of these formats, see article [What Image Formats are Available in 3Engines 3Engines Cloud cloud](What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md).
|
||||
For the explanation of these formats, see article [What Image Formats are Available in connectVM connectVM Cloud cloud](What-Image-Formats-are-available-in-connectVM-connectVM-Cloud-Cloud.html.md).
|
||||
|
||||
No. 3 **Uploaded public SSH key**
|
||||
|
||||
If the image you wish to upload requires you to attach an SSH public key while creating the virtual machine, the key will need to be uploaded to 3Engines Cloud cloud. One of these articles should help:
|
||||
If the image you wish to upload requires you to attach an SSH public key while creating the virtual machine, the key will need to be uploaded to connectVM Cloud cloud. One of these articles should help:
|
||||
@ -1,12 +1,12 @@
|
||||
How to upload your custom image using 3Engines CLI on 3Engines Cloud[🔗](#how-to-upload-your-custom-image-using-3Engines-cli-on-brand-name "Permalink to this headline")
|
||||
How to upload your custom image using connectVM CLI on connectVM Cloud[🔗](#how-to-upload-your-custom-image-using-connectVM-cli-on-brand-name "Permalink to this headline")
|
||||
===========================================================================================================================================================================
|
||||
|
||||
In this tutorial, you will upload custom image stored on your local computer to 3Engines Cloud cloud, using the 3Engines CLI client. The uploaded image will be available within your project alongside default images from 3Engines Cloud cloud and you will be able to create virtual machines using it.
|
||||
In this tutorial, you will upload custom image stored on your local computer to connectVM Cloud cloud, using the connectVM CLI client. The uploaded image will be available within your project alongside default images from connectVM Cloud cloud and you will be able to create virtual machines using it.
|
||||
|
||||
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------------
|
||||
|
||||
> * How to check for the presence of the image in your 3Engines cloud
|
||||
> * How to check for the presence of the image in your connectVM cloud
|
||||
> * How different images might behave
|
||||
> * How to upload the image using only CLI commands
|
||||
> * Example: how to upload image for Debian 11
|
||||
@ -17,11 +17,11 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with access to the Horizon interface: <https://console.connectvm.com/>.
|
||||
|
||||
No. 2 **3Engines CLI configured**
|
||||
No. 2 **connectVM CLI configured**
|
||||
|
||||
You need to have the 3Engines CLI client configured and operational. See [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md). You can test whether your 3Engines CLI is properly activated by executing the **3Engines server list** command mentioned in the end of that article - it should return the list of your virtual machines.
|
||||
You need to have the connectVM CLI client configured and operational. See [How to install connectVMClient for Linux on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md). You can test whether your connectVM CLI is properly activated by executing the **connectVM server list** command mentioned in the end of that article - it should return the list of your virtual machines.
|
||||
|
||||
No. 3 **Custom image you wish to upload**
|
||||
|
||||
@ -39,8 +39,8 @@ The following container formats are supported:
|
||||
> | aki | ami | ari | bare |
|
||||
> | docker | ova | ovf | |
|
||||
|
||||
For the explanation of these formats, see article [What Image Formats are Available in 3Engines 3Engines Cloud cloud](What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md).
|
||||
For the explanation of these formats, see article [What Image Formats are Available in connectVM connectVM Cloud cloud](What-Image-Formats-are-available-in-connectVM-connectVM-Cloud-Cloud.html.md).
|
||||
|
||||
No. 4 **Uploaded public SSH key**
|
||||
|
||||
If the image you wish to upload requires you to attach an SSH public key while creating the virtual machine, the key will need to be uploaded to 3Engines Cloud cloud. One of these articles should help:
|
||||
If the image you wish to upload requires you to attach an SSH public key while creating the virtual machine, the key will need to be uploaded to connectVM Cloud cloud. One of these articles should help:
|
||||
@ -1,7 +1,7 @@
|
||||
How to Use GUI in Linux VM on 3Engines Cloud and access it From Local Linux Computer[🔗](#how-to-use-gui-in-linux-vm-on-brand-name-and-access-it-from-local-linux-computer "Permalink to this headline")
|
||||
How to Use GUI in Linux VM on connectVM 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 3Engines Cloud cloud.
|
||||
In this article you will learn how to use GUI (graphical user interface) on a Linux virtual machine running on connectVM Cloud cloud.
|
||||
|
||||
For this purpose, you will install and use **X2Go** on your local Linux computer.
|
||||
|
||||
@ -20,7 +20,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with access to the Horizon interface: <https://console.connectvm.com/>.
|
||||
|
||||
No. 2 **Linux installed on your local computer**
|
||||
|
||||
@ -28,9 +28,9 @@ You need to have a local computer with Linux installed. This article was written
|
||||
|
||||
No. 3 **Linux virtual machine**
|
||||
|
||||
You need a Linux virtual machine running on 3Engines Cloud cloud. You need to able to access it via SSH. The following article explains how to create one such virtual machine:
|
||||
You need a Linux virtual machine running on connectVM Cloud cloud. You need to able to access it via SSH. The following article explains how to create one such virtual machine:
|
||||
|
||||
[How to create a Linux VM and access it from Linux command line on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md)
|
||||
[How to create a Linux VM and access it from Linux command line on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md)
|
||||
|
||||
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.
|
||||
|
||||
@ -1,7 +1,7 @@
|
||||
How to use Security Groups in Horizon on 3Engines Cloud[🔗](#how-to-use-security-groups-in-horizon-on-brand-name "Permalink to this headline")
|
||||
How to use Security Groups in Horizon on connectVM Cloud[🔗](#how-to-use-security-groups-in-horizon-on-brand-name "Permalink to this headline")
|
||||
===============================================================================================================================================
|
||||
|
||||
Security groups in **3Engines** are used to filter the Internet traffic coming **to** and **from** your virtual machines. They consist of security rules and can be attached to your virtual machines during and after the creation of the machines.
|
||||
Security groups in **connectVM** are used to filter the Internet traffic coming **to** and **from** your virtual machines. They consist of security rules and can be attached to your virtual machines during and after the creation of the machines.
|
||||
|
||||
By default, each instance has a rule which blocks all incoming Internet traffic and allows all outgoing traffic. To modify those settings, you can apply other security groups to it.
|
||||
|
||||
@ -10,7 +10,7 @@ Viewing the security groups[🔗](#viewing-the-security-groups "Permalink to thi
|
||||
|
||||
To check your current security groups, please follow these steps:
|
||||
|
||||
Log in to your 3Engines Cloud account: <https://3engine.rootxwire.com/>.
|
||||
Log in to your connectVM Cloud account: <https://console.connectvm.com/>.
|
||||
|
||||
In the panel on the left choose **Network** and then **Security Groups**.
|
||||
|
||||
@ -1,10 +1,10 @@
|
||||
Resizing a virtual machine using 3Engines Horizon on 3Engines Cloud[🔗](#resizing-a-virtual-machine-using-3Engines-horizon-on-brand-name "Permalink to this headline")
|
||||
Resizing a virtual machine using connectVM Horizon on connectVM Cloud[🔗](#resizing-a-virtual-machine-using-connectVM-horizon-on-brand-name "Permalink to this headline")
|
||||
=========================================================================================================================================================================
|
||||
|
||||
Introduction[🔗](#introduction "Permalink to this headline")
|
||||
-----------------------------------------------------------
|
||||
|
||||
When creating a new virtual machine under 3Engines, one of the options you choose is the *flavor*. A flavor is a predefined combination of CPU, memory and disk size and there usually is a number of such flavors for you to choose from.
|
||||
When creating a new virtual machine under connectVM, one of the options you choose is the *flavor*. A flavor is a predefined combination of CPU, memory and disk size and there usually is a number of such flavors for you to choose from.
|
||||
|
||||
After the instance is spawned, it is possible to change one flavor for another, and that process is called *resizing*. You might want to resize an already existing VM in order to:
|
||||
|
||||
@ -14,32 +14,32 @@ After the instance is spawned, it is possible to change one flavor for another,
|
||||
> * seamlessly transition from testing to production environment,
|
||||
> * change application workload byt scaling the VM up or down.
|
||||
|
||||
In this article, we are going to resize VMs using commands in 3Engines Horizon.
|
||||
In this article, we are going to resize VMs using commands in connectVM Horizon.
|
||||
|
||||
Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
-------------------------------------------------------------
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://portal.3Engines.com/>.
|
||||
You need a connectVM Cloud hosting account with access to the Horizon interface: <https://portal.connectVM.com/>.
|
||||
|
||||
No. 2 **How to create a new VM**
|
||||
|
||||
If you are a normal user of 3Engines Cloud hosting, you will have all prerogatives needed to resize the VM. Make sure that the VM you are about to resize belongs to a project you have access to. Here are the basics of creating a Linux VM in Horizon:
|
||||
If you are a normal user of connectVM Cloud hosting, you will have all prerogatives needed to resize the VM. Make sure that the VM you are about to resize belongs to a project you have access to. Here are the basics of creating a Linux VM in Horizon:
|
||||
|
||||
[How to create a Linux VM and access it from Linux command line on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md)
|
||||
[How to create a Linux VM and access it from Linux command line on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md)
|
||||
|
||||
[How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md)
|
||||
[How to create a Linux VM and access it from Windows desktop on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md)
|
||||
|
||||
No. 3 **Awareness of existing quotas and flavors limits**
|
||||
|
||||
For general introduction to quotas and flavors, see [Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md).
|
||||
For general introduction to quotas and flavors, see [Dashboard Overview – Project Quotas And Flavors Limits on connectVM Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md).
|
||||
|
||||
Also:
|
||||
|
||||
> * The VM you want to resize is in an active or shut down state.
|
||||
> * A flavor with the desired resource configuration exists.
|
||||
> * Adequate resources are available in your 3Engines environment to accommodate the resize.
|
||||
> * Adequate resources are available in your connectVM environment to accommodate the resize.
|
||||
|
||||
Creating a new VM[🔗](#creating-a-new-vm "Permalink to this headline")
|
||||
---------------------------------------------------------------------
|
||||
@ -131,4 +131,4 @@ In this case, the sizes of the disk before and after the resizing do not match.
|
||||
What To Do Next[🔗](#what-to-do-next "Permalink to this headline")
|
||||
-----------------------------------------------------------------
|
||||
|
||||
You can also resize the virtual machine using only 3Engines CLI. More details here: [Resizing a virtual machine using 3Engines CLI on 3Engines Cloud](../3Enginescli/Resizing-a-virtual-machine-using-3Engines-CLI-on-3Engines-Cloud.html.md)
|
||||
You can also resize the virtual machine using only connectVM CLI. More details here: [Resizing a virtual machine using connectVM CLI on connectVM Cloud](../connectVMcli/Resizing-a-virtual-machine-using-connectVM-CLI-on-connectVM-Cloud.html.md)
|
||||
@ -1,4 +1,4 @@
|
||||
Spot instances on 3Engines Cloud[🔗](#spot-instances-on-brand-name "Permalink to this headline")
|
||||
Spot instances on connectVM 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.
|
||||
@ -15,7 +15,7 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
No. 1 **Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://3engine.rootxwire.com/>
|
||||
You need a connectVM Cloud hosting account with access to the Horizon interface: <https://console.connectvm.com/>
|
||||
|
||||
No. 2 **Available exclusively on WAW3-2 cloud**
|
||||
|
||||
@ -25,8 +25,8 @@ When using spot instances, be sure to work only on WAW3-2 cloud:
|
||||
|
||||
No. 3 **Using quotas and flavors**
|
||||
|
||||
For quotas, see this article: [Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md)
|
||||
For quotas, see this article: [Dashboard Overview – Project Quotas And Flavors Limits on connectVM Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md)
|
||||
|
||||
No. 3 **3Engines CLI client**
|
||||
No. 3 **connectVM CLI client**
|
||||
|
||||
If you want to interact with 3Engines Cloud cloud using 3Engines CLI client, you need to have it installed. Check one of these articles:
|
||||
If you want to interact with connectVM Cloud cloud using connectVM CLI client, you need to have it installed. Check one of these articles:
|
||||
@ -1,7 +1,7 @@
|
||||
Status Power State and dependencies in billing of instance VMs on 3Engines Cloud[🔗](#status-power-state-and-dependencies-in-billing-of-instance-vms-on-brand-name "Permalink to this headline")
|
||||
Status Power State and dependencies in billing of instance VMs on connectVM Cloud[🔗](#status-power-state-and-dependencies-in-billing-of-instance-vms-on-brand-name "Permalink to this headline")
|
||||
=================================================================================================================================================================================================
|
||||
|
||||
In 3Engines, instances have their own Status and Power State:
|
||||
In connectVM, instances have their own Status and Power State:
|
||||
|
||||
> * **Status** informs about the present condition of the VM, while
|
||||
> * **Power** states tell us only whether virtual machines are running or not.
|
||||
@ -1,4 +1,4 @@
|
||||
VM created with option Create New Volume No on 3Engines 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 connectVM 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**”.
|
||||
@ -13,7 +13,7 @@ The new Virtual Machine will be created with the System Volume (Root Disk) size
|
||||
|
||||
|
||||
|
||||
If you want to select a different size for the System Volume (Root Disk) please read article [VM created with option Create New Volume Yes on 3Engines Cloud](VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md).
|
||||
If you want to select a different size for the System Volume (Root Disk) please read article [VM created with option Create New Volume Yes on connectVM Cloud](VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md).
|
||||
|
||||
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
VM created with option Create New Volume Yes on 3Engines 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 connectVM Cloud[🔗](#vm-created-with-option-create-new-volume-yes-on-brand-name "Permalink to this headline")
|
||||
=============================================================================================================================================================
|
||||
|
||||
Note
|
||||
@ -1,15 +1,15 @@
|
||||
What Image Formats are Available in 3Engines 3Engines Cloud cloud[🔗](#what-image-formats-are-available-in-3Engines-brand-name-cloud "Permalink to this headline")
|
||||
What Image Formats are Available in connectVM connectVM Cloud cloud[🔗](#what-image-formats-are-available-in-connectVM-brand-name-cloud "Permalink to this headline")
|
||||
=====================================================================================================================================================================
|
||||
|
||||
In 3Engines Cloud 3Engines ten image format extensions are available:
|
||||
In connectVM Cloud connectVM ten image format extensions are available:
|
||||
|
||||
**QCOW2** - Formatted Virtual Machine Storage is a storage format for virtual machine disk images. QCOW stands for “QEMU copy on write”. It is used with the KVM hypervisor. The images are typically smaller than RAW images, so it is often faster to convert a raw image to qcow2 for uploading instead of uploading the raw file directly. Because raw images do not support snapshots, 3Engines Compute will automatically convert raw image files to qcow2 as needed.
|
||||
**QCOW2** - Formatted Virtual Machine Storage is a storage format for virtual machine disk images. QCOW stands for “QEMU copy on write”. It is used with the KVM hypervisor. The images are typically smaller than RAW images, so it is often faster to convert a raw image to qcow2 for uploading instead of uploading the raw file directly. Because raw images do not support snapshots, connectVM Compute will automatically convert raw image files to qcow2 as needed.
|
||||
|
||||
**RAW** - The RAW storage is the simplest one, and is natively supported by both KVM and Xen hypervisors. RAW image could be considered as the bit-equivalent of a block device file. It has a performance advantage over QCOW2 in that no formatting is applied to virtual machine disk images stored in the RAW format. No additional work from hosts is required in Virtual machine data operations on disk images stored in this format.
|
||||
|
||||
**ISO** - The ISO format is a disk image formatted with the read-only ISO 9660 filesystem which is used for CDs and DVDs. While ISO is not frequently considered as a virtual machine image format, because of ISOs contain bootable filesystems with an installed operating system, it can be treated like other virtual machine image files.
|
||||
|
||||
**VDI** - Virtual Disk Image format used by VirtualBox for image files. None of the 3Engines Compute hypervisors supports VDI directly, so it will be needed to convert these files to a different format to use them.
|
||||
**VDI** - Virtual Disk Image format used by VirtualBox for image files. None of the connectVM Compute hypervisors supports VDI directly, so it will be needed to convert these files to a different format to use them.
|
||||
|
||||
**VHD** - Virtual Hard Disk format for images, widely used by Microsoft (e.g. Hyper-V, Microsoft Virtual PC).
|
||||
|
||||
@ -1,23 +0,0 @@
|
||||
What is an 3Engines project on 3Engines Cloud[🔗](#what-is-an-3Engines-project-on-brand-name "Permalink to this headline")
|
||||
=============================================================================================================================
|
||||
|
||||
A **project** is a isolated group of zero or more users who share common access with specific privileges to the software instance in 3Engines. A project is created for each set of instances and networks that are configured as a discrete entity for the project. In Compute, a project owns virtual machines (in Compute) or containers (in Object Storage).
|
||||
|
||||
You can imagine that the whole 3Engines cloud is a big cake of resources (vCPU, disks, instances, etc…) and projects are the pieces of this cake served to the customers.
|
||||
|
||||
Current project name is **visible** in the Horizon panel.
|
||||
|
||||
|
||||
|
||||
Projects are created, managed, and edited at the 3Engines **Projects** screen.
|
||||
|
||||
|
||||
|
||||
Users can be associated with more than one project, but once signed, they can only see and access the resources available in that project.
|
||||
Each project and user pairing can have a role associated with it.
|
||||
|
||||
3Engines users can create projects, and create new accounts using the 3Engines Dashboard. They can also associate other users with roles, projects, or both.
|
||||
|
||||
To remove project its mandatory to manually remove all of its resources first.
|
||||
|
||||
Users can create private networks for connectivity within projects [How to create a network with router in Horizon Dashboard on 3Engines Cloud](../networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-3Engines-Cloud.html.md). By default, they are fully isolated and are not shared with other projects.
|
||||
@ -1,15 +1,15 @@
|
||||
What is an 3Engines domain on 3Engines Cloud[🔗](#what-is-an-3Engines-domain-on-brand-name "Permalink to this headline")
|
||||
What is an connectVM domain on connectVM Cloud[🔗](#what-is-an-connectVM-domain-on-brand-name "Permalink to this headline")
|
||||
===========================================================================================================================
|
||||
|
||||
**Domain**
|
||||
|
||||
Intention of providing a domain in cloud environment is to define boundaries for management. 3Engines domain is a type of a container for projects, users and groups.
|
||||
Intention of providing a domain in cloud environment is to define boundaries for management. connectVM domain is a type of a container for projects, users and groups.
|
||||
One crucial benefit is separating overlapping resource names for different domains.
|
||||
Furthermore, permissions in the project and domain are two not related things, hereby customization for administrator is made up much easier.
|
||||
|
||||
Current domain name is **visible** beside the project that is currently selected in the Horizon panel.
|
||||
|
||||
|
||||
|
||||
|
||||
The name of the domain is grayed out, denoting that you can use only the domain that has been allocated to you by the system.
|
||||
|
||||
@ -17,10 +17,10 @@ You cannot create a new domain.
|
||||
|
||||
**Service relation**
|
||||
|
||||
3Engines Cloud account is linked to your main account in particular domain, hence it allows you to login to the 3Engines dashboard without any need to deliver keystone credentials.
|
||||
connectVM Cloud account is linked to your main account in particular domain, hence it allows you to login to the connectVM dashboard without any need to deliver keystone credentials.
|
||||
|
||||
This type of facility is due to a proper implementation of KeyCloak and KeyStone relation.
|
||||
|
||||
**Docs**
|
||||
|
||||
Click here if you want to see official [3Engines documentation for domains](https://docs.3Engines.org/security-guide/identity/domains.html.md).
|
||||
Click here if you want to see official [connectVM documentation for domains](https://docs.connectVM.org/security-guide/identity/domains.html.md).
|
||||
@ -0,0 +1,23 @@
|
||||
What is an connectVM project on connectVM Cloud[🔗](#what-is-an-connectVM-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 connectVM. A project is created for each set of instances and networks that are configured as a discrete entity for the project. In Compute, a project owns virtual machines (in Compute) or containers (in Object Storage).
|
||||
|
||||
You can imagine that the whole connectVM cloud is a big cake of resources (vCPU, disks, instances, etc…) and projects are the pieces of this cake served to the customers.
|
||||
|
||||
Current project name is **visible** in the Horizon panel.
|
||||
|
||||
|
||||
|
||||
Projects are created, managed, and edited at the connectVM **Projects** screen.
|
||||
|
||||
|
||||
|
||||
Users can be associated with more than one project, but once signed, they can only see and access the resources available in that project.
|
||||
Each project and user pairing can have a role associated with it.
|
||||
|
||||
connectVM users can create projects, and create new accounts using the connectVM Dashboard. They can also associate other users with roles, projects, or both.
|
||||
|
||||
To remove project its mandatory to manually remove all of its resources first.
|
||||
|
||||
Users can create private networks for connectivity within projects [How to create a network with router in Horizon Dashboard on connectVM Cloud](../networking/How-to-create-a-network-with-router-in-Horizon-Dashboard-on-connectVM-Cloud.html.md). By default, they are fully isolated and are not shared with other projects.
|
||||
@ -2,37 +2,37 @@
|
||||
|
||||
## Available Documentation
|
||||
|
||||
* [Dashboard Overview – Project Quotas And Flavors Limits on 3Engines Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-3Engines-Cloud.html.md)
|
||||
* [How to access the VM from 3Engines console on 3Engines Cloud](How-to-access-the-VM-from-3Engines-console-on-3Engines-Cloud.html.md)
|
||||
* [How to clone existing and configured VMs on 3Engines Cloud](How-to-clone-existing-and-configured-VMs-on-3Engines-Cloud.html.md)
|
||||
* [How to fix unresponsive console issue on 3Engines Cloud](How-to-fix-unresponsive-console-issue-on-3Engines-Cloud.html.md)
|
||||
* [How to generate and manage EC2 credentials on 3Engines Cloud](How-to-generate-ec2-credentials-on-3Engines-Cloud.html.md)
|
||||
* [How to generate or use Application Credentials via CLI on 3Engines Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md)
|
||||
* [How to Use GUI in Linux VM on 3Engines Cloud and access it From Local Linux Computer](How-to-use-GUI-in-Linux-VM-on-3Engines-Cloud-and-access-it-from-local-Linux-computer.html.md)
|
||||
* [How To Create a New Linux VM With NVIDIA Virtual GPU in the 3Engines Dashboard Horizon on 3Engines Cloud](How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md)
|
||||
* [How to install and use Docker on Ubuntu 24.04](How-to-use-Docker-on-3Engines-Cloud.html.md)
|
||||
* [How to use Security Groups in Horizon on 3Engines Cloud](How-to-use-Security-Groups-in-Horizon-on-3Engines-Cloud.html.md)
|
||||
* [How to create key pair in 3Engines Dashboard on 3Engines Cloud](How-to-create-key-pair-in-3Engines-Dashboard-on-3Engines-Cloud.html.md)
|
||||
* [How to create new Linux VM in 3Engines Dashboard Horizon on 3Engines Cloud](How-to-create-new-Linux-VM-in-3Engines-Dashboard-Horizon-on-3Engines-Cloud.html.md)
|
||||
* [How to install Python virtualenv or virtualenvwrapper on 3Engines Cloud](How-to-install-Python-virtualenv-or-virtualenvwrapper-on-3Engines-Cloud.html.md)
|
||||
* [How to start a VM from a snapshot on 3Engines Cloud](How-to-start-a-VM-from-a-snapshot-on-3Engines-Cloud.html.md)
|
||||
* [Status Power State and dependencies in billing of instance VMs on 3Engines Cloud](Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-3Engines-Cloud.html.md)
|
||||
* [How to upload your custom image using 3Engines CLI on 3Engines Cloud](How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md)
|
||||
* [VM created with option Create New Volume No on 3Engines Cloud](VM-created-with-option-Create-New-Volume-No-on-3Engines-Cloud.html.md)
|
||||
* [VM created with option Create New Volume Yes on 3Engines Cloud](VM-created-with-option-Create-New-Volume-Yes-on-3Engines-Cloud.html.md)
|
||||
* [What is an 3Engines domain on 3Engines Cloud](What-is-an-3Engines-domain-on-3Engines-Cloud.html.md)
|
||||
* [What is an 3Engines project on 3Engines Cloud](What-is-an-3Engines-project-on-3Engines-Cloud.html.md)
|
||||
* [How to create a Linux VM and access it from Windows desktop on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-3Engines-Cloud.html.md)
|
||||
* [How to create a Linux VM and access it from Linux command line on 3Engines Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-3Engines-Cloud.html.md)
|
||||
* [DNS as a Service on 3Engines Cloud Hosting](DNS-as-a-Service-on-3Engines-Cloud-Hosting.html.md)
|
||||
* [What Image Formats are Available in 3Engines 3Engines Cloud cloud](What-Image-Formats-are-available-in-3Engines-3Engines-Cloud-Cloud.html.md)
|
||||
* [How to upload custom image to 3Engines Cloud cloud using 3Engines Horizon dashboard](How-to-upload-custom-image-to-3Engines-Cloud-cloud-using-3Engines-Horizon-dashboard.html.md)
|
||||
* [How to create Windows VM on 3Engines Horizon and access it via web console on 3Engines Cloud](How-to-create-Windows-VM-on-3Engines-Horizon-and-access-it-via-web-console-on-3Engines-Cloud.html.md)
|
||||
* [How to transfer volumes between domains and projects using Horizon dashboard on 3Engines Cloud](How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-3Engines-Cloud.html.md)
|
||||
* [Spot instances on 3Engines Cloud](Spot-instances-on-3Engines-Cloud.html.md)
|
||||
* [How to create instance snapshot using Horizon on 3Engines Cloud](How-to-create-instance-snapshot-using-Horizon-on-3Engines-Cloud.html.md)
|
||||
* [How to start a VM from instance snapshot using Horizon dashboard on 3Engines Cloud](How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-3Engines-Cloud.html.md)
|
||||
* [How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud](How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md)
|
||||
* [3Engines User Roles on 3Engines Cloud](3Engines-user-roles-on-3Engines-Cloud.html.md)
|
||||
* [Resizing a virtual machine using 3Engines Horizon on 3Engines Cloud](Resizing-a-virtual-machine-using-3Engines-Horizon-on-3Engines-Cloud.html.md)
|
||||
* [Block storage and object storage performance limits on 3Engines Cloud](Block-storage-and-object-storage-performance-limits-on-3Engines-Cloud.html.md)
|
||||
* [Dashboard Overview – Project Quotas And Flavors Limits on connectVM Cloud](Dashboard-Overview-Project-Quotas-And-Flavors-Limits-on-connectVM-Cloud.html.md)
|
||||
* [How to access the VM from connectVM console on connectVM Cloud](How-to-access-the-VM-from-connectVM-console-on-connectVM-Cloud.html.md)
|
||||
* [How to clone existing and configured VMs on connectVM Cloud](How-to-clone-existing-and-configured-VMs-on-connectVM-Cloud.html.md)
|
||||
* [How to fix unresponsive console issue on connectVM Cloud](How-to-fix-unresponsive-console-issue-on-connectVM-Cloud.html.md)
|
||||
* [How to generate and manage EC2 credentials on connectVM Cloud](How-to-generate-ec2-credentials-on-connectVM-Cloud.html.md)
|
||||
* [How to generate or use Application Credentials via CLI on connectVM Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md)
|
||||
* [How to Use GUI in Linux VM on connectVM Cloud and access it From Local Linux Computer](How-to-use-GUI-in-Linux-VM-on-connectVM-Cloud-and-access-it-from-local-Linux-computer.html.md)
|
||||
* [How To Create a New Linux VM With NVIDIA Virtual GPU in the connectVM Dashboard Horizon on connectVM Cloud](How-To-Create-a-New-Linux-VM-With-NVIDIA-Virtual-GPU-in-the-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md)
|
||||
* [How to install and use Docker on Ubuntu 24.04](How-to-use-Docker-on-connectVM-Cloud.html.md)
|
||||
* [How to use Security Groups in Horizon on connectVM Cloud](How-to-use-Security-Groups-in-Horizon-on-connectVM-Cloud.html.md)
|
||||
* [How to create key pair in connectVM Dashboard on connectVM Cloud](How-to-create-key-pair-in-connectVM-Dashboard-on-connectVM-Cloud.html.md)
|
||||
* [How to create new Linux VM in connectVM Dashboard Horizon on connectVM Cloud](How-to-create-new-Linux-VM-in-connectVM-Dashboard-Horizon-on-connectVM-Cloud.html.md)
|
||||
* [How to install Python virtualenv or virtualenvwrapper on connectVM Cloud](How-to-install-Python-virtualenv-or-virtualenvwrapper-on-connectVM-Cloud.html.md)
|
||||
* [How to start a VM from a snapshot on connectVM Cloud](How-to-start-a-VM-from-a-snapshot-on-connectVM-Cloud.html.md)
|
||||
* [Status Power State and dependencies in billing of instance VMs on connectVM Cloud](Status-Power-State-and-dependences-in-billing-of-instances-VMs-on-connectVM-Cloud.html.md)
|
||||
* [How to upload your custom image using connectVM CLI on connectVM Cloud](How-to-upload-your-custom-image-using-connectVM-CLI-on-connectVM-Cloud.html.md)
|
||||
* [VM created with option Create New Volume No on connectVM Cloud](VM-created-with-option-Create-New-Volume-No-on-connectVM-Cloud.html.md)
|
||||
* [VM created with option Create New Volume Yes on connectVM Cloud](VM-created-with-option-Create-New-Volume-Yes-on-connectVM-Cloud.html.md)
|
||||
* [What is an connectVM domain on connectVM Cloud](What-is-an-connectVM-domain-on-connectVM-Cloud.html.md)
|
||||
* [What is an connectVM project on connectVM Cloud](What-is-an-connectVM-project-on-connectVM-Cloud.html.md)
|
||||
* [How to create a Linux VM and access it from Windows desktop on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Windows-desktop-on-connectVM-Cloud.html.md)
|
||||
* [How to create a Linux VM and access it from Linux command line on connectVM Cloud](How-to-create-a-Linux-VM-and-access-it-from-Linux-command-line-on-connectVM-Cloud.html.md)
|
||||
* [DNS as a Service on connectVM Cloud Hosting](DNS-as-a-Service-on-connectVM-Cloud-Hosting.html.md)
|
||||
* [What Image Formats are Available in connectVM connectVM Cloud cloud](What-Image-Formats-are-available-in-connectVM-connectVM-Cloud-Cloud.html.md)
|
||||
* [How to upload custom image to connectVM Cloud cloud using connectVM Horizon dashboard](How-to-upload-custom-image-to-connectVM-Cloud-cloud-using-connectVM-Horizon-dashboard.html.md)
|
||||
* [How to create Windows VM on connectVM Horizon and access it via web console on connectVM Cloud](How-to-create-Windows-VM-on-connectVM-Horizon-and-access-it-via-web-console-on-connectVM-Cloud.html.md)
|
||||
* [How to transfer volumes between domains and projects using Horizon dashboard on connectVM Cloud](How-to-transfer-volumes-between-domains-and-projects-using-Horizon-dashboard-on-connectVM-Cloud.html.md)
|
||||
* [Spot instances on connectVM Cloud](Spot-instances-on-connectVM-Cloud.html.md)
|
||||
* [How to create instance snapshot using Horizon on connectVM Cloud](How-to-create-instance-snapshot-using-Horizon-on-connectVM-Cloud.html.md)
|
||||
* [How to start a VM from instance snapshot using Horizon dashboard on connectVM Cloud](How-to-start-a-VM-from-instance-snapshot-using-Horizon-dashboard-on-connectVM-Cloud.html.md)
|
||||
* [How to create a VM using the connectVM CLI client on connectVM Cloud cloud](How-to-create-a-VM-using-the-connectVM-CLI-client-on-connectVM-Cloud-cloud.html.md)
|
||||
* [connectVM User Roles on connectVM Cloud](connectVM-user-roles-on-connectVM-Cloud.html.md)
|
||||
* [Resizing a virtual machine using connectVM Horizon on connectVM Cloud](Resizing-a-virtual-machine-using-connectVM-Horizon-on-connectVM-Cloud.html.md)
|
||||
* [Block storage and object storage performance limits on connectVM Cloud](Block-storage-and-object-storage-performance-limits-on-connectVM-Cloud.html.md)
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
3Engines User Roles on 3Engines Cloud[🔗](#3Engines-user-roles-on-brand-name "Permalink to this headline")
|
||||
connectVM User Roles on connectVM Cloud[🔗](#connectVM-user-roles-on-brand-name "Permalink to this headline")
|
||||
=============================================================================================================
|
||||
|
||||
A **user role** in 3Engines cloud is a set of permissions that govern how members of specific groups interact with system resources, their access scope, and capabilities.
|
||||
A **user role** in connectVM 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 3Engines roles for casual users of 3Engines Cloud VMs. It focuses on practical use cases and commonly required roles.
|
||||
This guide simplifies connectVM roles for casual users of connectVM 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")
|
||||
---------------------------------------------------------------------------------------
|
||||
@ -28,28 +28,28 @@ Prerequisites[🔗](#prerequisites "Permalink to this headline")
|
||||
|
||||
**1. Account**
|
||||
|
||||
You need a 3Engines Cloud hosting account with Horizon access: <https://3engine.rootxwire.com/>.
|
||||
You need a connectVM Cloud hosting account with Horizon access: <https://console.connectvm.com/>.
|
||||
|
||||
Also see:
|
||||
|
||||
[What is an 3Engines project on 3Engines Cloud](What-is-an-3Engines-project-on-3Engines-Cloud.html.md)
|
||||
[What is an connectVM project on connectVM Cloud](What-is-an-connectVM-project-on-connectVM-Cloud.html.md)
|
||||
|
||||
[What is an 3Engines domain on 3Engines Cloud](What-is-an-3Engines-domain-on-3Engines-Cloud.html.md)
|
||||
[What is an connectVM domain on connectVM Cloud](What-is-an-connectVM-domain-on-connectVM-Cloud.html.md)
|
||||
|
||||
[How to generate or use Application Credentials via CLI on 3Engines Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md)
|
||||
[How to generate or use Application Credentials via CLI on connectVM Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md)
|
||||
|
||||
**2. Familiarity with 3Engines Commands**
|
||||
**2. Familiarity with connectVM Commands**
|
||||
|
||||
Ensure you know the following 3Engines commands:
|
||||
Ensure you know the following connectVM commands:
|
||||
|
||||
**3Engines**
|
||||
: The primary CLI for interacting with 3Engines services.
|
||||
[How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md)
|
||||
**connectVM**
|
||||
: The primary CLI for interacting with connectVM services.
|
||||
[How to install connectVMClient for Linux on connectVM Cloud](../connectVMcli/How-to-install-connectVMClient-for-Linux-on-connectVM-Cloud.html.md)
|
||||
|
||||
**kubectl**
|
||||
: CLI for Kubernetes clusters. Example article:
|
||||
|
||||
[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud 3Engines Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-3Engines-Magnum.html.md)
|
||||
[How To Access Kubernetes Cluster Post Deployment Using Kubectl On connectVM Cloud connectVM Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-connectVM-Cloud-connectVM-Magnum.html.md)
|
||||
|
||||
Frequently used user roles[🔗](#frequently-used-user-roles "Permalink to this headline")
|
||||
---------------------------------------------------------------------------------------
|
||||
@ -61,22 +61,22 @@ Frequently used user roles[🔗](#frequently-used-user-roles "Permalink to this
|
||||
|
||||
Note
|
||||
|
||||
Older 3Engines versions may use **\_member\_**. If both **member** and **\_member\_** exist, choose **member**.
|
||||
Older connectVM versions may use **\_member\_**. If both **member** and **\_member\_** exist, choose **member**.
|
||||
|
||||
* Horizon: **Project** -> **Overview**
|
||||
* CLI: **3Engines server list**, **3Engines project list**
|
||||
* CLI: **connectVM server list**, **connectVM project list**
|
||||
|
||||
**observer**
|
||||
: Read-only access for monitoring and auditing resources. Suitable for third-party tools like Prometheus or Grafana.
|
||||
|
||||
* Horizon: **Project** -> **Overview**
|
||||
* CLI: **3Engines server show**, **3Engines project show**
|
||||
* CLI: **connectVM server show**, **connectVM project show**
|
||||
|
||||
**reader**
|
||||
: Read-only access with slightly broader permissions than **observer**. Ideal for monitoring and analytics tools requiring detailed resource data.
|
||||
|
||||
* Horizon: **Project** -> **Overview**
|
||||
* CLI: **3Engines server list**, **3Engines project list**
|
||||
* CLI: **connectVM server list**, **connectVM project list**
|
||||
|
||||
### Roles for Kubernetes users[🔗](#roles-for-kubernetes-users "Permalink to this headline")
|
||||
|
||||
@ -104,13 +104,13 @@ Frequently used user roles[🔗](#frequently-used-user-roles "Permalink to this
|
||||
: Grants access to deploy applications behind load balancers.
|
||||
|
||||
* Horizon: **Network** -> **Load Balancers**
|
||||
* CLI: **3Engines loadbalancer member create**, **3Engines loadbalancer member list**
|
||||
* CLI: **connectVM loadbalancer member create**, **connectVM loadbalancer member list**
|
||||
|
||||
**load-balancer\_observer**
|
||||
: Read-only access to monitor load balancer configurations.
|
||||
|
||||
* Horizon: **Network** -> **Load Balancers**
|
||||
* CLI: **3Engines loadbalancer show**, **3Engines loadbalancer stats show**
|
||||
* CLI: **connectVM loadbalancer show**, **connectVM loadbalancer stats show**
|
||||
|
||||
How to View Roles in Horizon[🔗](#how-to-view-roles-in-horizon "Permalink to this headline")
|
||||
-------------------------------------------------------------------------------------------
|
||||
@ -123,7 +123,7 @@ You can view roles in Horizon by navigating to **Identity** -> **Roles**.
|
||||
|
||||
Assigning multiple roles is best done during project creation rather than user creation.
|
||||
|
||||
|
||||
|
||||
|
||||
Examples of using user roles[🔗](#examples-of-using-user-roles "Permalink to this headline")
|
||||
-------------------------------------------------------------------------------------------
|
||||
@ -132,7 +132,7 @@ The following articles, as one of many steps, describe how to assign a role to t
|
||||
|
||||
### Using user roles while creating application credential in Horizon[🔗](#using-user-roles-while-creating-application-credential-in-horizon "Permalink to this headline")
|
||||
|
||||
Normally, you access the cloud via user credentials, which may be one- or two-factor credentials. 3Engines provides a more direct procedure of gaining access to cloud with application credential and you can create a credential with several user roles.
|
||||
Normally, you access the cloud via user credentials, which may be one- or two-factor credentials. connectVM provides a more direct procedure of gaining access to cloud with application credential and you can create a credential with several user roles.
|
||||
|
||||
That S3 article selects user roles when creating an application credential, through Horizon:
|
||||
|
||||
@ -144,7 +144,7 @@ That S3 article selects user roles when creating an application credential, thro
|
||||
|
||||
This is the main article about application credentials; it is mostly using CLI:
|
||||
|
||||
[How to generate or use Application Credentials via CLI on 3Engines Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-3Engines-Cloud.html.md)
|
||||
[How to generate or use Application Credentials via CLI on connectVM Cloud](How-to-generate-or-use-Application-Credentials-via-CLI-on-connectVM-Cloud.html.md)
|
||||
|
||||
Here is how to specify user roles through CLI parameters:
|
||||
|
||||
@ -152,14 +152,14 @@ Here is how to specify user roles through CLI parameters:
|
||||
|
||||
### Using user roles while creating a new project[🔗](#using-user-roles-while-creating-a-new-project "Permalink to this headline")
|
||||
|
||||
In article [How to Create and Configure New 3Engines Project Through Horizon on 3Engines Cloud Cloud](../3Enginescli/How-To-Create-and-Configure-New-Project-on-3Engines-Cloud-Cloud.html.md) we use command **Project Members** to define which users to include into the project:
|
||||
In article [How to Create and Configure New connectVM Project Through Horizon on connectVM Cloud Cloud](../connectVMcli/How-To-Create-and-Configure-New-Project-on-connectVM-Cloud-Cloud.html.md) we use command **Project Members** to define which users to include into the project:
|
||||
|
||||
|
||||
|
||||
You would then continue by defining the roles for each user in the project:
|
||||
|
||||
|
||||
> See this Rancher article, [How to install Rancher RKE2 Kubernetes on 3Engines Cloud](../kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-3Engines-Cloud-cloud.html.md). Then, in Preparation step 1, a new project is created, with the following user roles:
|
||||
> See this Rancher article, [How to install Rancher RKE2 Kubernetes on connectVM Cloud](../kubernetes/How-to-install-Rancher-RKE2-Kubernetes-on-connectVM-Cloud-cloud.html.md). Then, in Preparation step 1, a new project is created, with the following user roles:
|
||||
|
||||
* **load-balancer\_member**,
|
||||
* **member** and
|
||||
@ -169,9 +169,9 @@ You would then continue by defining the roles for each user in the project:
|
||||
|
||||
### Using member role only while creating a new user[🔗](#using-member-role-only-while-creating-a-new-user "Permalink to this headline")
|
||||
|
||||
In SLURM article, we first create a new 3Engines Keystone user, with the role of **member**.
|
||||
In SLURM article, we first create a new connectVM Keystone user, with the role of **member**.
|
||||
|
||||
/cuttingedge/Sample-SLURM-Cluster-on-3Engines-Cloud-Cloud-with-ElastiCluster
|
||||
/cuttingedge/Sample-SLURM-Cluster-on-connectVM-Cloud-Cloud-with-ElastiCluster
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user