How to access the VM from OpenStack console on 3Engines Cloud[🔗](#how-to-access-the-vm-from-openstack-console-on-brand-name "Permalink to this headline")
===========================================================================================================================================================

Once you have created a virtual machine in OpenStack, you will need to perform various administrative tasks such as:

> * installing and uninstalling software,
> * uploading and downloading files,
> * setting up passwords and access policies

and so on. There are three ways to enter the back end part of virtual machines:

**Linux**
:   For Linux, either of the Ubuntu or CentOS variety, you will be using the console that is present with every VM. You enter the console as a predefined user called **eoconsole**, define the password and switch to another, also predefined, user called **eouser**. After that, each time you are use the console, you will be present as **eouser**.

**Windows**
:   You only need to create an *Administrator* profile within the virtual machine. Once you do that, you will work with Windows just like on the desktop computer, with possible delays in response due to the speed of Internet connection you have.

**Fedora**
:   Fedora images technically belong to the family of Linux operating systems, but cannot be accessed via the console. To be more precise, you will see the console but won’t be able to log in as the standard **eoconsole** user.

    As these images are only used for automatic creation of Kubernetes instances, you have to enter them using Kubernetes methods. That boils down to using **kubectl exec** command (see below).

What We Are Going To Cover[🔗](#what-we-are-going-to-cover "Permalink to this headline")
---------------------------------------------------------------------------------------

> * Use console for Linux based virtual machines
> * Use console for Windows based virtual machines
> * Use console for Fedora base virtual machines

Prerequisites[🔗](#prerequisites "Permalink to this headline")
-------------------------------------------------------------

No. 1 **Account**

You need a 3Engines Cloud hosting account with access to the Horizon interface: <https://horizon.3Engines.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://horizon.3Engines.com> and select your authentication method:

![login_3Enginescloud.png](../_images/login_3Enginescloud.png)

You will enter the Horizon main screen.

2. Open the **Compute/Instances** tab and select the desired VM by clicking on its name:

![accessvm2.png](../_images/accessvm2.png)

3. Select **“Console”** pane

![accessvm3.png](../_images/accessvm3.png)

4. When logging in for the first time, you will see the generic console screen:

![accessvm4v2.png](../_images/accessvm4v2.png)

Click on link **Click here to show only console** and then click on the console surface to make it active.

Enter the predefined user name **eoconsole**. You will be asked to set up a new password, twice. This user **eoconsole** serves only for you to enter the console.

The next step is to start using another user, called **eouser**. Just like **eoconsole**, it is already defined for you, so you only need to switch from **eoconsole** to **eouser**. Linux command to do that is

```
sudo su - eouser

```

![sudo_su_eouser.png](../_images/sudo_su_eouser.png)

You will then use the console as a predefined user called **eouser**.

Attention

Google Chrome seems to work slowly while using the OpenStack console. Firefox works well.

Using console to perform administrative tasks within Fedora VMs[🔗](#using-console-to-perform-administrative-tasks-within-fedora-vms "Permalink to this headline")
-----------------------------------------------------------------------------------------------------------------------------------------------------------------

For normal VMs, choose either Ubuntu- or CentOS-based images while creating a VM – but not Fedora. It is meant only for automatic creation of instances that belong to Kubernetes clusters. Such instances will have either word *master* or *node* in their names. Here is a typical series of instances that belong to two different clusters, called *vault* and *k8s-23*:

![some_nodes.png](../_images/some_nodes.png)

So if you click on any of these Kubernetes instances, you will be able to enter the console but will not be able to use it. In this context, Fedora image is **intentionally** set up in such a way that you **cannot enter it through the console**. You will, typically, see this after Fedora starts:

![fedora_image.png](../_images/fedora_image.png)

Instead, it is possible to enter one such instance using main Kubernetes command, **kubectl** with parameter **exec**. The main command would look like this:

```
kubectl -n vault exec -it vault-0 -- sh

```

where *vault* is the namespace within which the pod *vault-0* will be found and entered.

Further explanations of **exec** command are out of scope of this article. The following article will show you how to activate the **kubectl** command after the cluster has been created:

[How To Access Kubernetes Cluster Post Deployment Using Kubectl On 3Engines Cloud OpenStack Magnum](../kubernetes/How-To-Access-Kubernetes-Cluster-Post-Deployment-Using-Kubectl-On-3Engines-Cloud-OpenStack-Magnum.html.md)

This article shows an example of an **exec** command to enter the VM and, later, save the data within it:

[Volume-based vs Ephemeral-based Storage for Kubernetes Clusters on 3Engines Cloud OpenStack Magnum](../kubernetes/Volume-based-vs-Ephemeral-based-Storage-for-Kubernetes-Clusters-on-3Engines-Cloud-OpenStack-Magnum.html.md)

### Performing administrative tasks within Windows based VMs[🔗](#performing-administrative-tasks-within-windows-based-vms "Permalink to this headline")

In case of **Windows** set a new password for *Administrator* profile.

![accessvm5.png](../_images/accessvm5.png)

You will then be able to perform administrative tasks on your instance.