Briefly: it is not possible. Each user, while creating CREODIAS account is identified by his mail address given during the registration process.

The mail address is equivalent for user login in clients database. For this reason, our billing and provisioning systems won't allow duplicates for avoiding issues related to confusing the same logins with several tenants.

What is more, in this case, security system sees no difference between a main account and sub-account, which causes that user with a domain created with one login cannot be subaccount using the same mail address.

Please note that this issue takes place only on CREODIAS platform and Client Area. In Horizon Dashboard each domain can contain the same user which should log in via Keystone credentials and provide a number of the domain in the login procedure.

Here you can see also how to register a new account, how to add new subaccount and how to add new user in the Horizon Dashboard

By default, in our platform Linux hosts have the highest size of IP data packet payload (Maximum Transmission Unit) set as 8950 bytes by DHCP server.

It does not have any impact on the speed of internet connection, but it may optimize connectivity with EOData network.

Unfortunately, Windows VMs does not respect this DHCP setting, and at least so far, Windows users have to switch it manually.

To do so, please click the Start button, and enter cmd command. You will see the Windows command line. After that, check your existing and attached network interfaces by executing:

netsh interface ipv4 show interfaces

You will see output like this:

After that, perform the ipconfig command to see  what IP is attached to the particular interface.

In this example, I will focus on Ethernet 3 adapter with EOData network IP address (10.111.0.207) attached.

To increase MTU payload, execute the command

netsh interface ipv4 set subinterface "Ethernet 3" mtu=8950 store=persistent 

where "Ethernet 3" is the name of the desired network and "mtu" is the size of packet measured in bytes

After that, check the correctness of operation by checking interfaces list again.

First, it is required to log in on CREODIAS in order to download satellite products. Click “Log In” button

You will be moved to login site and asked to enter your login and password.

Click “Data & Analytics” and choose EOFinder

Select desired product (by entering REST query or finding it by in-built search engine, as explained here

Click on product path in “Search Results” panel

Choose “Download” icon

Now you will be able to download product to your computer.

As well as using graphic interface of EOFinder, you can browse and download satellite products by s3cmd, s3fs and boto3 using terminal:

How to mount EO DATA using s3fs?
How to mount EO DATA using s3 protocol?

How to access EO DATA using s3cmd?
How to download EO DATA file using boto3?

It is a common problem with using additional volumes if we have created a new instance with a real volume before. After performing a particular operation, our virtual machine is unable to boot.

This article splits up in two sections: reproduction of the issue and workaround for CREODIAS users.

Reproduction:

1. Create a virtual machine with a new real root disk.

2. Click on the name of your instance.

3. Verify the type of the disk. It has been set up as vda. (Within a virtual machine it is visible as sda)

4. Create additional volume and attach it to the Instance. It has been set up as sda. (Within a virtual machine it is visible as sdb)

5. If you choose one of those options: [...]

• Shelve Instance

• Soft Reboot Instance

• Hard Reboot Instance

Your instance will become unavailable to boot:

Why did it happen? The additional volume (which does not contain any OS) has been chosen as a sda device during booting this time.

Solution:

To overcome this issue, you have to create a virtual machine with real root disk using Openstack CLI.

1. Source your RC file and use this command to create a bootable volume:

User@CREODIAS:~$ openstack volume create --image image_id --size 5 name_of_the_volume

2. As you may see, you have created a bootable volume with Image Ubuntu 18.04.

3. Now you can create a virtual machine:

User@CREODIAS:~$ openstack server create --volume volume_id --flavor flavor_name --key-name key_name --security-group security_group_id --network network_id name_of_the_virtual_machine

4. The instance has been deployed. Go to Instance details.

Attached volume has a proper sda prefix.

You can access visual applications in two ways:

• X11 forwarding
• X2GO (NX standard)

X11 forwarding

The simplest (but inefficient for intense pixel graphics, as in satellite imagery analysis programs) is X-over-ssh.  The window of a single application is just displayed on terminal screen.

To allow X11 forwarding:

make sure that /etc/ssh/sshd_config on the virtual machine contains:

X11Forwarding yes
X11DisplayOffset 10

Now you can establish an ssh session including -X parameter:

user@CREODIAS:~$ ssh -X eouser@instance_ip

From manual:

-X Enables X11 forwarding. This can also be specified on a per-host basis in a configuration file.
X11 forwarding should be enabled with caution.
Users with the ability to bypass file permissions on the remote host (for the user's X authorization database) can access the local X11 display through the forwarded connection.
An attacker may then be able to perform activities such as keystroke monitoring.

X2GO

Other solution is NX standard which, however, requires X2Go software, which is not supported directly by linux distributions. Nevertheless, it can be used and many people prefer it over VNC.  Clients are available for linux, Windows, and Mac. You can gather more information in separate article:

How to use GUI in VM with Linux?

The installation and configuration is well guided on X2Go official site

http://wiki.x2go.org/doku.php