Environment Management
Manage the environment around the database, such as Cloud, Monitoring, Exaoperation and scalability
cancel
Showing results for 
Search instead for 
Did you mean: 
Docker is a PaaS "Platform as a Service" product that uses OS-level virtualization technology to deploy software in relatively small packages called containers that are completely isolated, have their own software, libraries, and even network. Exasol supports Docker as a platform and you can easily obtain our image via Github or Docker Hub. This tutorial below will show you how to install Docker on Ubuntu and other Debian-based systems (however, the installed repo will vary). NOTE: This method was tested on Ubuntu Server 18.04 (Bionic Beaver) and 20.04 ( Focal Fossa) 1. Update your Packages list: $ sudo apt update 2. Install the necessary packages: $ sudo apt install apt-transport-https ca-certificates curl software-properties-common - 3. Add the GPG keys for the Docker repository: $ curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add - 4. Add the official Docker repository: $ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable" (for 18.04) $ sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu focal stable" (for 20.04) 5. Update the new packages list (you should see the Docker package list being downloaded): $ sudo apt update 6. Install Docker Community Edition: $ sudo apt install docker-ce -y 7. Check if Docker is running: $ sudo systemctl status docker 7.1. If not running, run the following commands: $ sudo systemctl start docker $ sudo systemctl enable docker 8. Run the "Hello World" container to verify: $ docker run hello-world ... Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (amd64) 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal.  9. Download other images via: $ docker image pull <image_name>  After you finish the steps above you are ready to continue with installing your Exasol system. You can do so by following the instructions at How to Deploy a Single-Node Exasol Database as a Docker Image for Testing Purposes.
View full article
Docker is a PaaS "Platform as a Service" product that uses OS-level virtualization technology to deploy software in relatively small packages called containers that are completely isolated, have their own software, libraries, and even network. Exasol supports Docker as a platform and you can easily obtain our image via Github or Docker Hub. This tutorial below will show you how to install Docker on CentOS and other RHEL-based systems (however, the installed repo will vary). NOTE: This method was tested on CentOS 7.7 1. Update your Packages list: $ sudo yum update 2. Install the necessary packages: $ sudo yum install -y yum-utils device-mapper-persistent-data lvm2 3. Add the official Docker repository: $ sudo yum-config-manager --add-repo https://download.docker.com/linux/centos/docker-ce.repo for CentOS $ sudo yum-config-manager --add-repo https://download.docker.com/linux/rhel/docker-ce.repo for RHEL $ sudo yum-config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo for Fedora 4. Update the new packages list (you should see the Docker package list being downloaded): $ sudo yum update 5. Install Docker Community Edition: $ sudo yum install docker-ce -y 6. Check if Docker is running: $ sudo systemctl status docker 6.1. If not running, run the following commands: $ sudo systemctl start docker $ sudo systemctl enable docker 7. Run the "Hello World" container to verify: $ docker run hello-world ... Hello from Docker! This message shows that your installation appears to be working correctly. To generate this message, Docker took the following steps: 1. The Docker client contacted the Docker daemon. 2. The Docker daemon pulled the "hello-world" image from the Docker Hub. (amd64) 3. The Docker daemon created a new container from that image which runs the executable that produces the output you are currently reading. 4. The Docker daemon streamed that output to the Docker client, which sent it to your terminal.  8. Download other images via: $ docker image pull <image_name> After you finish the steps above you are ready to continue with installing your Exasol system. You can do so by following the instructions at How to Deploy a Single-Node Exasol Database as a Docker Image for Testing Purposes.
View full article
Background In this tutorial we are going to show you how to create a BucketFS and Buckets inside it for Exasol on Docker. Prerequisites Access to the Docker host Access to firewall/cloud management console to open port (in our example, AWS will be used) Very basic knowledge of the curl command How to create a BucketFS and Buckets inside it In this section, we will show you the whole process of: Creating a BucketFS Creating a bucket inside it (Optional) Opening the required port(s) in the AWS management console for newly created BucketFS Committing the Changes Uploading some files via the curl command   Step 1. Go to your Docker host, log in to the container and create a BucketFS Log in to your host via ssh (or console) and get inside your Exasol on Docker container: $ docker exec -it <your_exasol_container_name> /bin/bash You can find the container's name by running docker ps. Once inside the container run the following command to create a BucketFS: $ exaconf add-bucketfs --name newbucketfs* --http-port 6932** --https-port 0*** --owner 500:500 * - This will be the name of your new BucketFS ** - This will be the port for communicating via HTTP *** - This will be the port for communicating via HTTPS This will create the BucketFS config required in the /exa/etc/EXAConf file.   Step 2. Create a bucket inside your newly created BucketFS Once the BucketFS is created run the following command to create the bucket inside the aforementioned BucketFS: $ exaconf add-bucket --name newbucketfs-bucket* --bfs-name newbucketfs** --read-passwd $(echo -n "newread"*** | base64) --write-passwd $(echo -n "newwrite"**** | base64) * - This will be the name of your new Bucket ** - This is the name of your newly created BucketFS *** - This will be your new password for read (r) **** - This will be your new password for write (w) Once the bucket is created, open the /exa/etc/EXAConf file and check if you can see the newly added BucketFS/Bucket there: $ cat /exa/etc/EXAConf Output should be similar to:   Step 3. (Optional) Open the firewall port for the new BucketFS (in this example, AWS) Go to the Security Group that you used while deploying the Docker node and add the port that you used for the new BucketFS:   1 - Go to the Secuirty Group and edit the inbound rules 2 - When in the security group rules' configuration press Add Rule 3 - Select Custom TCP add the port number and the source address 4 - Save the changes If you are using an other cloud provider please check their documentation on how to open ports for services.   Step 4. Committing the Changes Once the changes are done, run the following command inside the container: $ sed -i '/Checksum =/c\ Checksum = COMMIT' /exa/etc/EXAConf Once that is done, run the following command: $ exaconf commit Once the commit is done your new bucket should be available via the curl command.   Step 5. Using the curl command to upload/download/delete To upload a file via curl use: $ curl -X PUT -T testfile.jar http://w:newwrite@<docker_host_ip>:6932/newbucketfs-bucket/testfile.jar To delete a file via curl use: $ curl -X DELETE http://w:newwrite@34.243.141.132:6932/newbucketfs-bucket/testfile.jar To list the contents of the bucket: $ curl http://r:newread@<docker_host_ip>:6932/newbucketfs-bucket/    
View full article
Background The tables below list the default ports of network services and DBMSs with which the EXASOL database may communicate. Notes Many of the following protocols and DBMSs can be manually configured to use different ports. The File Transfer Protocol (FTP) data connections require additional ports to be available (depending on the transfer mode). Explanation   Incoming Connections   Protocol Port Source Destination Description TCP 8563 EXASOL Client EXASOL database nodes EXASOL server port TCP Range from 20000 to 21000 EXASOL database nodes (source) EXASOL database nodes (target) EXASOL sub connection ports (for EXA-to-EXA loading)     Outgoing Connections   Protocol Port Source Destination Description TCP 8563 EXASOL database nodes EXASOL database client EXASOL database client connection port TCP Range from 20000 to 21000 EXASOL database nodes (source) EXASOL database nodes (target) EXASOL subconnection ports (for EXA-to-EXA loading) TCP 20 EXASOL database nodes FTP server FTP data port for IMPORT/EXPORT TCP 21 EXASOL database nodes FTP server FTP command port for IMPORT/EXPORT TCP 22 EXASOL database nodes SFTP server SFTP port for IMPORT/EXPORT TCP 80 EXASOL database nodes HTTP server HTTP port for IMPORT/EXPORT TCP 443 EXASOL database nodes HTTPS server HTTPS port for IMPORT/EXPORT TCP 990 EXASOL database nodes FTPS server FTPS port for IMPORT/EXPORT TCP 389 EXASOL nodes LDAP server LDAP port TCP 636 EXASOL nodes LDAPS server LDAPS port TCP 1521 EXASOL database nodes Oracle database Oracle server port (JDBC/ORA connection) TCP 1433 EXASOL database nodes SQL Server database SQL Server server port (JDBC connection) TCP 3306 EXASOL database nodes MySQL database MySQL server port (JDBC connection) TCP 50000 EXASOL database nodes DB2 database DB2 server port (JDBC connection) TCP 5432 EXASOL database nodes PostgreSQL database PostgreSQL server port (JDBC connection) TCP 5000 EXASOL database nodes Sybase ASE database Sybase ASE server port (JDBC connection)   Additional References https://docs.exasol.com/administration/on-premise/installation/prepareenvironment/cluster_networking_infrastructure.htm?Highlight=network
View full article
Certified Hardware List
The hardware certified by Exasol can be found in the link below:

Certified Hardware List

If your preferred hardware is not certified, refer to our Certification Process for more information on this process.
Top Contributors