How to activate OpenStack CLI access to 3Engines Cloud cloud using one- or two-factor authentication[🔗](#how-to-activate-openstack-cli-access-to-brand-name-cloud-using-one-or-two-factor-authentication "Permalink to this headline")
How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication[🔗](#how-to-activate-3Engines-cli-access-to-brand-name-cloud-using-one-or-two-factor-authentication "Permalink to this headline")
One-factor and two-factor authentication for activating command line access to the cloud[🔗](#one-factor-and-two-factor-authentication-for-activating-command-line-access-to-the-cloud "Permalink to this headline")
@ -13,7 +13,7 @@ To log into a site, you usually provide user name and email address during the c
> * to generate six-digit code using the appropriate software and then to
> * send it to the cloud as a means of additional certification.
Cloud parameters for authentication and, later, OpenStack CLI access, are found in a so-called *RC file*. This article will help you download and use it to first authenticate and then access the cloud using OpenStack CLI commands.
Cloud parameters for authentication and, later, 3Engines CLI access, are found in a so-called *RC file*. This article will help you download and use it to first authenticate and then access the cloud using 3Engines CLI commands.
What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
@ -41,18 +41,18 @@ If your account has 2FA enabled (which you will recognize from the respective pr
* Mobile device (Android, iOS): [Two-Factor Authentication to 3Engines Cloud site using mobile application](Two-Factor-Authentication-for-3Engines-Cloud-Site.html.md)
* Computer [Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop](Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.md)
No. 3 **OpenStackClient installed and available**
No. 3 **3EnginesClient installed and available**
Installing OpenStackClient on various platforms will also install the ability to run the **.sh** files. Since OpenStack is written in Python, it is recommended to use a dedicated virtual environment for the rest of this article.
Installing 3EnginesClient on various platforms will also install the ability to run the **.sh** files. Since 3Engines is written in Python, it is recommended to use a dedicated virtual environment for the rest of this article.
Install GitBash on Windows
: Run **.sh** files and install OpenStackClient from a GitBash window under Windows. [How to install OpenStackClient GitBash for Windows on 3Engines Cloud](../openstackcli/How-to-install-OpenStackClient-GitBash-or-Cygwin-for-Windows-on-3Engines-Cloud.html.md).
: Run **.sh** files and install 3EnginesClient from a GitBash window under 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).
Install and run WSL (Linux under Windows)
: Run **.sh** files and install OpenStackClient from a Ubuntu window under Windows. [How to install OpenStackClient on Windows using Windows Subsystem for Linux on 3Engines Cloud OpenStack Hosting](../openstackcli/How-to-install-OpenStackClient-on-Windows-using-Windows-Subsystem-for-Linux-on-3Engines-Cloud-OpenStack-Hosting.html.md).
: Run **.sh** files and install 3EnginesClient from a Ubuntu window 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).
Install OpenStackClient on Linux
: [How to install OpenStackClient for Linux on 3Engines Cloud](../openstackcli/How-to-install-OpenStackClient-for-Linux-on-3Engines-Cloud.html.md).
Install 3EnginesClient on Linux
: [How to install 3EnginesClient for Linux on 3Engines Cloud](../3Enginescli/How-to-install-3EnginesClient-for-Linux-on-3Engines-Cloud.html.md).
How to download the RC file[🔗](#how-to-download-the-rc-file "Permalink to this headline")
You only need one copy of the RC file at any time. If you downloaded more than one copy of the file to the same folder without moving or renaming them, your operating system may differentiate amongst the downloaded files by adding additional characters at the end of the file name.
@ -99,7 +99,7 @@ By way of example, let the downloaded RC file name be **cloud\_00734\_1-openrc-2
The contents of the downloaded RC file[🔗](#the-contents-of-the-downloaded-rc-file "Permalink to this headline")
RC file sets up *environment variables* which are used by the OpenStack CLI client to authenticate to the cloud. By convention, these variables are in upper case and start with **OS\_**: **OS\_TENANT\_ID**, **OS\_PROJECT\_NAME** etc. For example, in case of one-factor authentication, the RC file will ask for password and store it into a variable called **OS\_PASSWORD**.
RC file sets up *environment variables* which are used by the 3Engines CLI client to authenticate to the cloud. By convention, these variables are in upper case and start with **OS\_**: **OS\_TENANT\_ID**, **OS\_PROJECT\_NAME** etc. For example, in case of one-factor authentication, the RC file will ask for password and store it into a variable called **OS\_PASSWORD**.
Below is an example content of an RC file which does not use 2FA:
@ -175,15 +175,15 @@ Duration of life for environment variables set by sourcing the RC file[🔗](#du
When you source the file, environment variables are set for your current shell. To prove it, open two terminal windows, source the RC file in one of them but not in the other and you won’t be able to authenticate from that second terminal window.
That is why you will need to activate your RC file each time you start a new terminal session. Once authenticated and while that terminal window is open, you can use it to issue OpenStack CLI commands at will.
That is why you will need to activate your RC file each time you start a new terminal session. Once authenticated and while that terminal window is open, you can use it to issue 3Engines CLI commands at will.
Testing the connection[🔗](#testing-the-connection "Permalink to this headline")
If not already, install OpenStack client using one of the links in Prerequisite No 3. To verify access, execute the following command which lists flavors available in 3Engines Cloud cloud:
If not already, install 3Engines client using one of the links in Prerequisite No 3. To verify access, execute the following command which lists flavors available in 3Engines Cloud cloud:
```
openstack flavor list
3Engines flavor list
```
@ -236,7 +236,7 @@ To resolve this issue, please connect to the Internet and try to activate the RC
### Non-2FA accounts: entering a wrong password[🔗](#non-2fa-accounts-entering-a-wrong-password "Permalink to this headline")
If your account does not have two-factor authentication and you entered a wrong password, you will **not** get an error. However, if you try to execute a command like **openstack flavor list**, you will get the error similar to this:
If your account does not have two-factor authentication and you entered a wrong password, you will **not** get an error. However, if you try to execute a command like **3Engines flavor list**, you will get the error similar to this:
```
The request you have made requires authentication. (HTTP 401) (Request-ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
@ -249,7 +249,7 @@ To resolve, activate your file again and enter the correct password.
### Using the wrong file[🔗](#using-the-wrong-file "Permalink to this headline")
If you have a 2FA authentication enabled for your account but have tried to activate the non-2FA version of the RC file, executing, say, command **openstack flavor list**, will give you the following error:
If you have a 2FA authentication enabled for your account but have tried to activate the non-2FA version of the RC file, executing, say, command **3Engines flavor list**, will give you the following error:
```
Unrecognized schema in response body. (HTTP 401)
@ -268,12 +268,12 @@ With the appropriate version of RC file activated, you should be able to create
> * networks,
> * Kubernetes clusters
and, in general, use all OpenStack CLI commands.
and, in general, use all 3Engines CLI commands.
For example, if you want to create a new virtual machine, you can follow this article:
[How to create a VM using the OpenStack CLI client on 3Engines Cloud cloud](../cloud/How-to-create-a-VM-using-the-OpenStack-CLI-client-on-3Engines-Cloud-cloud.html.md)
[How to create a VM using the 3Engines CLI client on 3Engines Cloud cloud](../cloud/How-to-create-a-VM-using-the-3Engines-CLI-client-on-3Engines-Cloud-cloud.html.md)
If you want your new virtual machine to be based on an image which is not available on 3Engines Cloud cloud, you will need to upload it. The following article contains instructions how to do it:
[How to upload your custom image using OpenStack CLI on 3Engines Cloud](../cloud/How-to-upload-your-custom-image-using-OpenStack-CLI-on-3Engines-Cloud.html.md)
[How to upload your custom image using 3Engines CLI on 3Engines Cloud](../cloud/How-to-upload-your-custom-image-using-3Engines-CLI-on-3Engines-Cloud.html.md)
At the moment of this writing, there were four different regions to choose from: WAW3-1, WAW3-2, WAW4-1, FRA1-2. These regions are actually clouds running under OpenStack and in each you can have your own virtual machines, access to EO data, create Kubernetes clusters and so on. Although all clouds are running under OpenStack, there are differences in available software, hardware, resources and so on, so it pays to learn which cloud is best for you.
At the moment of this writing, there were four different regions to choose from: WAW3-1, WAW3-2, WAW4-1, FRA1-2. These regions are actually clouds running under 3Engines and in each you can have your own virtual machines, access to EO data, create Kubernetes clusters and so on. Although all clouds are running under 3Engines, there are differences in available software, hardware, resources and so on, so it pays to learn which cloud is best for you.
You may want to work with all these clouds at the same time, maybe with different groups of people working on different projects and so on.
Tenant manager users and roles on 3Engines Cloud[](#tenant-manager-users-and-roles-on-3Engines-cloud "Permalink to this headline")enant manager users and roles on 3Engines Cloud[🔗](#tenant-manager-users-and-roles-on-brand-name "Permalink to this headline")
Differences between OpenStack User Roles and Tenant Manager’s Roles[🔗](#differences-between-openstack-user-roles-and-tenant-manager-s-roles "Permalink to this headline")
Differences between 3Engines User Roles and Tenant Manager’s Roles[🔗](#differences-between-3Engines-user-roles-and-tenant-manager-s-roles "Permalink to this headline")
An OpenStack role is a personality that a user assumes to perform a specific set of operations. A role includes a set of rights and privileges. A user assuming that role inherits those rights and privileges. OpenStack roles are defined for each user and each project independently.
An 3Engines role is a personality that a user assumes to perform a specific set of operations. A role includes a set of rights and privileges. A user assuming that role inherits those rights and privileges. 3Engines roles are defined for each user and each project independently.
A Tenant Manager role, on the other hand, defines whether a user should have the ability to manage an organization via the Tenant Manager or have access to OpenStack.
A Tenant Manager role, on the other hand, defines whether a user should have the ability to manage an organization via the Tenant Manager or have access to 3Engines.
What Are We Going To Cover[🔗](#what-are-we-going-to-cover "Permalink to this headline")
As an *organization administrator* you can assign one of the following roles to a user:
> * **admin** - user with highest privileges, can manage whole organizations and has access to OpenStack.
> * **admin** - user with highest privileges, can manage whole organizations and has access to 3Engines.
> * **member** - default user with basic privileges.
> * **member+** - the same as **member** but has OpenStack access and can manage projects.
> * **member+** - the same as **member** but has 3Engines access and can manage projects.
Adding member+ user to your project in OpenStack using Horizon interface[🔗](#adding-member-user-to-your-project-in-openstack-using-horizon-interface "Permalink to this headline")
Adding member+ user to your project in 3Engines using Horizon interface[🔗](#adding-member-user-to-your-project-in-3Engines-using-horizon-interface "Permalink to this headline")
Users with the role of **member+** have access to OpenStack and can be enabled to manage your organization projects. They cannot however, manage the organization itself.
Users with the role of **member+** have access to 3Engines and can be enabled to manage your organization projects. They cannot however, manage the organization itself.
To add a **member+** user to the project, follow these steps:
@ -64,7 +64,7 @@ To add a **member+** user to the project, follow these steps:
@ -208,6 +208,6 @@ If the FreeOTP app is in the foreground on the mobile device while you are submi
As mentioned in the beginning, you can use your computer for two-factor authentication – see article [Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop](Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.md).
Either using mobile device or computer to authenticate, you will be logged into Horizon. You will then need to activate access to 3Engines Cloud cloud API functions and be able to run **openstack** command. Please see article [How to activate OpenStack CLI access to 3Engines Cloud cloud using one- or two-factor authentication](How-to-activate-OpenStack-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md).
Either using mobile device or computer to authenticate, you will be logged into Horizon. You will then need to activate access to 3Engines Cloud cloud API functions and be able to run **3Engines** command. Please see article [How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md).
To learn how to manage your TOTP secret key, visit the following article: [How to manage TOTP authentication on 3Engines Cloud](How-to-manage-TOTP-authentication-on-3Engines-Cloud.html.md) - it can be useful if you, for instance, want to use a different method of authentication, are unable to extract your secret key from currently used piece of software such as FreeOTP and do not have your secret key backed up in a readable way.
@ -9,7 +9,7 @@ ACCOUNT MANAGEMENT[](#account-management "Permalink to this headline")
* [How to start using dashboard services on 3Engines Cloud](How-to-start-using-dashboard-services-on-3Engines-Cloud.html.md)
* [Two-Factor Authentication to 3Engines Cloud site using mobile application](Two-Factor-Authentication-for-3Engines-Cloud-Site.html.md)
* [Two-Factor Authentication to 3Engines Cloud site using KeePassXC on desktop](Using-KeePassXC-for-Two-Factor-Authentication-on-3Engines-Cloud.html.md)
* [How to activate OpenStack CLI access to 3Engines Cloud cloud using one- or two-factor authentication](How-to-activate-OpenStack-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md)
* [How to activate 3Engines CLI access to 3Engines Cloud cloud using one- or two-factor authentication](How-to-activate-3Engines-CLI-access-to-3Engines-Cloud-cloud-using-one-or-two-factor-authentication.html.md)
* [How to manage TOTP authentication on 3Engines Cloud](How-to-manage-TOTP-authentication-on-3Engines-Cloud.html.md)
* [Adding and editing Organization](Adding-Editing-Organizations.html.md)
* [How to buy credits using Pay Per Use wallet on 3Engines Cloud](How-to-buy-credits-using-pay-per-use-wallet-on-3Engines-Cloud.html.md)
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
govardhan