There are no tags associated with this article.

Your Guide to Pay-Per-Use services

If you are using services that are billed in Pay-Per-Use mode, you can experience the situation, when your credits would be running low.

In such case, you will receive email notification from our billing system when your account balance will be lower than 50 credits.

If you run out of credits, you will get another email.
If your account overdraft will fall below -100  credits, all your instances will be paused.
If you do not buy additional credits, your virtual resources will be deleted after 30 days.

You can always buy new credits through our site here
If you have any problems or questions please contact our support

S3FS Cache

By default, S3FS Cache is enabled in CREODIAS preconfigured Linux images. To examine its directory location you might take a look at the configuration in /etc/fstab.

#s3fs#DIAS /eodata fuse passwd_file=/root/.passwd-s3fs,_netdev,allow_other,use_path_request_style,uid=0,umask=0222,mp_umask=0222,mp_umask=0222,gid=0,stat_cache_expire=20,url=http://data.cloudferro.com,use_cache=1,max_stat_cache_size=60000,list_object_max_keys=10000 0 0

Use_cache parameter points on the folder “1” (it is located at the beginning of Filesystem Hierarchy /)
From the manual pages:

-o use_cache (default="" which means disabled)
local folder to use for local file cache.

Directory “1” is being filled up during processing or downloading products from EOData repository to your local storage directly.

To avoid the situation when you cannot remount your resources because the cache directory is occupying a whole left space on the disk, you might try to set a parameter ensure_diskfree.

Common prompt messages when you cannot remount an /eodata:

clnt_create: RPC: Timed out
s3fs: There is no enough disk space for used as cache(or temporary) directory by s3fs.

From s3 manual pages, you can find out about ensure_diskfree parameter.

-o ensure_diskfree(default 0)
	sets MB to ensure disk free space. This option means the threshold of free space size on disk which is used for the cache file by s3fs. s3fs makes file for downloading, and uploading and caching files. If the disk free space is smaller than this value, s3fs do not use diskspace as possible in exchange for the performance.

How to create SSH Key Pair in Windows?

To create SSH key pair (private and public) in Windows you need to install puttygen.exe application.
You can download it from http://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html.
After installation please run puttygen.exe.

Click "Generate" button and move the mouse cursor randomly over the blank area.


You will obtain the following screen.

Mark and copy the text from the field under the title "Public key for pasting into OpenSSH authorized_keys file".
Open the notepad and paste the whole text into new file.


Save the file in the location of your choice (eg. C:\temp) and give the file a name (eg. key-01.pub).


ATTENTION: the above method works well with Openstack.
If instead of copy-and-paste you save the public key by clicking "Save public key" in puttygen.exe, the key will not be accepted by Openstack (it has different format from that in the field under the title "Public key for pasting into OpenSSH authorized_keys file").

Login to https://creodias.eu and go to Compute  -> Key Pairs


Click "Import Key Pair".


Give the new Key Pair the name (eg. key-01).
Paste the public key (obtained with puttygen.exe and saved in separate file) into Public Key field.


Click "Import Key Pair" button.
If you go to Compute -> Access & Security, you will see the new Key Pair on the list.


Come back to puttygen.exe application and click "Save private key" button.
Save the key in the location of your choice (eg. C:\temp) and give the key name (eg. key-01-priv).
The private key should be saved with the extension .ppk (eg. key-01-priv.ppk).


Using the private key and the puTTY.exe application you can login to the VM.

If you would like to learn more about PuTTYgen, learn about the installation or usage guide, we invite you to visit the website www.puttygen.com

What is the difference between Portal user (portal.creodias.eu) and OpenStack Dashboard (Horizon) user?

There are two different groups of users.

  1. The User of CREODIAS Portal (main account or subaccount):

  • is able to check the invoicing;
  • has access to the billing statistics;
  • may communicate with support team by using ticketing system;
  • can place order for additional credit units;
  • is able to add another user in the same domain (main account);
  • can buy services, which are not available in Horizon (e.g. bare metal machines, fixed term services).


By registering to CREODIAS portal the main account is created and the user automatically obtains an account in OpenStack Dashboard.

Portal overview:

Logging site:

Here you can sign in and make an account.

Checking the account settings. Click on the "My Account" button in the upper-right-corner:

Choose "Account Home" label.

Here you can monitor statistics of your running services, opened tickets etc.

  • Support – Here you can verify the status of your tickets.

  • Billing – Check the general info regarding billing per usage in your domain and percentage in whole credit expenditure.

  • Invoicing – Check your invoices and payment status.

In Contacts/Subaccounts field click on the "Update" button to add subaccount to our domain:


Subaccounts created in CREODIAS Portal have no access to the Horizon dashboard. Only the main account has access to Horizon account.

2. OpenStack (Horizon) user:

  • is capable of performing operations on virtual machines;
  • is able to use OpenStack CLI to monitor behaviour of instances;
  • can gain access to virtual machines via SPICE terminal (Horizon Console);
  • can generate ec2 credentials for object storage (See:  How to generate ec2 credentials?

OpenStack (Horizon) user overview

You can login to Horizon at:  https://cf2.cloudferro.com

Click on "OpenID Connect" and choose "Keystone Credentials".

You can also access the Horizon account from CREODIAS portal.

Click on the "Your Cloud Environment" in "My Account" tab.

Choose OpenID Connect.

In Compute → Overview you may check all diagrams showing your Limit Summary (Quota for particular resources). You can also see resource usage (Usage Summary) determined by selected time interval.

We can see the users having access to the project by clicking on "Identity" tab and choosing "Users" option.

In the example above John Doe is the main account. It means that John Doe has got two accounts: one in Horizon (OpenStack Dashboard) and one in CREODIAS Portal.

By clicking on the chosen user you will see additional information:


Clicking on the "Edit" button allows you to modify user's data.

You can also create new user that will have access to the project by clicking on "Create User" button.

How to Add/Remove Floating IP’s to your VM?

To make your VM accessible from the Internet you probably use or want to use Floating IP’s. Floating IP’s in Openstack are public IP adressess assigned to your Virtual Machine. The name is a bit misleading, because those adresses are permanent, they are not changing (as the name „floating” may suggest) once assigned to the VM. Assigning Floating IP can allow you (assuming you have Security Groups set properly) to host services like SSH, HTTP or other over the Internet.


How to assign Floating IP to your VM:

In Instances tab in Horizon, click the dropdown menu next to your VM and choose „Associate Floating IP”


You will be shown a window like this one:

You may choose an address from dropdown menu, but if its empty, you need to allocate an adress first. Click "+" icon on the right.

Click "Allocate IP"

Notice: the IP Adress should be associated with local adress from "192.168.x.x" subnet. If you have "10.x.x.x" address change it to "192.168.x.x" address.

Click "Associate".

You now have public IP assigned to your instance and visible in Instances menu:

You can now connect to your Virtual Machine trough SSH or RDP from the Internet.

Notice: The VM's communicate between themselve trough internal network "192.168.x.x" so if you are connecting from one Virtual Machine to another you should use private adresses.


How to dissasociate Floating IP:

If you no longer need public IP address you may dissasociate it from your VM. Click "Dissasociate Floating IP" from the dropdown menu:


How to release Floating IP (return it to the pool)

Floating IP’s as any other Openstack resources have their cost when kept reserved and not used.

If you dont want to keep your Floating IP’s reserved for your project you may release them to the Openstack pool for other users which will also reduce your project costs.

Go to Project → Network → Floating IPs

For the adress that is not in use the "Release Floating IP" option will be avaliable. Click it to release the IP address.