INUVIKA OVD INSTALLING INUVIKA OVD ON UBUNTU (TRUSTY TAHR)

Transcription

1 INUVIKA OVD INSTALLING INUVIKA OVD ON UBUNTU (TRUSTY TAHR) Mathieu SCHIRES Version: Published December 24,

2 Contents 1 Prerequisites: Ubuntu (Trusty Tahr) System Requirements Prerequisites for network sudo Repository 5 3 OVD Session Manager Installation and Configuration Installing MySQL Package Installation Configuration Setting Up the Subsystem Archive Installing the OVD Application Server and OVD File Server (using Subsystem) Important note Installation Setting a Redirection Name Installing an OVD Web Access (eg web.test.demo) 10 Page 1

3 The purpose of this document is to describe how the different server roles of Inuvika OVD can be installed on Ubuntu (Trusty Tahr) system. Page 2

4 1 PREREQUISITES: UBUNTU (TRUSTY TAHR) Ubuntu (Trusty Tahr) is an LTS version of Ubuntu. There are several editions: desktop/server, 32/64 bits. This documentation has been created for the 64 bits server edition but it should also work width the desktop edition. The Ubuntu operating system can be downloaded here. 1.1 SYSTEM REQUIREMENTS For an OVD Session Manager (OSM): Evaluations/POCs: Minimum prerequisites are 1 CPU core and 512MB RAM Production environments: Inuvika recommends a minimum of 2GB RAM and 2 CPU cores For an OVD Application Server (OAS): Evaluations/POCs: Minimum prerequisites are 1 CPU core and 1GB RAM Production environments: Inuvika recommends a minimum of 4GB RAM and 2 CPU cores For an OVD Web Access (OWA): Evaluations/POCs: Minimum prerequisites are 1 CPU core and 512MB RAM Production envrionments: Inuvika recommends 1GB RAM whenever possible or more For using the same physical machine to host the OSM, the OVD Web Access and the OAS: Evaluations/POCs: Minimum prerequisites are 1 CPU core and 1GB RAM Production environments: Please note, Inuvika does not recommend using this installation method for production environments 1.2 PREREQUISITES FOR NETWORK You need to review the "Protocol Overview" documentation to make sure that your firewalls are well configured 1.3 SUDO On Ubuntu systems, we are not using the super user (root) to log in and install packages. It is recomended to use sudo. So there are two alternatives: either you think about adding sudo before each command you launch or you log in as root To log in as root: $ sudo -s Page 3

5 In this document, we are using sm.test.demo for the OSM address, aps.test.demo for the OAS and web.test.demo for the OVD Web Access. You need to use the names that are configured for your own environment. Page 4

6 2 REPOSITORY Ubuntu (Trusty Tahr) is a Debian-based system which uses the same packaging system and tools: apt-get. So you need to have an internet connection on your Ubuntu (Trusty Tahr) system and add an Inuvika Debian repository to your system. Edit the /etc/apt/sources.list.d/ovd.list file and add these lines: deb trusty main Completing the Installation Process Install the keyring package to validate the repository using gpg: # wget -O- " apt-key add - Update the package database: # apt-get update Page 5

7 3 OVD SESSION MANAGER INSTALLATION AND CONFIGURATION The OSM is a LAMP (Linux Apache MySQL PHP) system and can be used on an exising LAMP server. 3.1 INSTALLING MYSQL The OSM needs access to a MySQL database. We advise you to setup the MySQL server on the same machine as the OSM to minimize access time. Install the mysql-server package: # apt-get install mysql-server A password for root will be asked. Now login to mysql and create a database: # mysql -u root -p -e 'create database ovd' 3.2 PACKAGE INSTALLATION Install the inuvika-ovd-session-manager packages: # apt-get install inuvika-ovd-session-manager inuvika-ovd-administration-\ console The installer requires the location of the OVD Session Manager The installer requires an admin login and a password which has to be confirmed. As described in the Archictecture documentation, a Susbsystem archive can be installed on the SM to simplify Application Server deployments. If you don t have access to the Internet, please read this to manually get the subsystem archive. The server is now installed but not configured yet. To configure the SM, open test.demo/ovd/admin in a web browser. 3.3 CONFIGURATION The first step is to go to and authenticate yourself width the login and password you provided during installation. The first time you log in, the system detects that it is not configured so you are redirected to a basic setup page which will save a default configuration. You have to set the MySQL configuration. For example, if you install MySQL on the same host as described previously, you would use the following configuration: Page 6

8 Database Type: MySQL Database host address: Database username: root Database password: [root_password] Database name: ovd Table prefix: ovd_ The OSM is now installed. Please read the appropriate documentations to install other servers or start sessions. 3.4 SETTING UP THE SUBSYSTEM ARCHIVE If you didn t specify a URL when initailly prompted, you have to manually copy a subsystem archive into /var/cache/ovd/session-manager/ovd-subsystem.tar.gz. Retrieve the ovd-subsystem.tar.gz archive from the Inuvika website and copy it into the /var/cache/ovd/sessionmanager/ folder of your machine. Page 7

9 4 INSTALLING THE OVD APPLICATION SERVER AND OVD FILE SERVER (USING SUBSYSTEM) 4.1 IMPORTANT NOTE Due to issues with the latest kernel, it s necessary to downgrade it. You have to use a Linux kernel version in your host server Define the Ubuntu precise repository cat >/etc/apt/sources.list.d/ubuntu-precise.list <<EOF deb precise main EOF Install the previous kernel # sudo apt-get update # sudo apt-get install linux-image virtual linux-image-extra\ virtual List all kernels installed # dpkg -l grep linux-image Remove all kernels higher than linux-image # sudo apt-get remove --purge linux-image-xxx You must reboot the server now 4.2 INSTALLATION Install the package inuvika-ovd-subsystem: # apt-get install inuvika-ovd-subsystem The only information required is the host/ip address where the OSM can be accessed (we use sm.test.demo here for the example, but of course, you have to set your own domain name). If you are going to install an OAS on the same machine as your OSM, it is recommended to use as the host. The configuration is now done. The system is going to download and uncompress the application system archive from the OVD Session Manager you registered. Once done, you just have to restart the service: Page 8

10 # /etc/init.d/ovd-subsystem restart Your server should appear in the Unregistered server page SETTING A REDIRECTION NAME The server redirection name is optional. If all your machines are in the same network, you don t have to change it. If you have installed your OAS on the same machine as your OSM and you have followed our advice, you have set as the server name so you must define a redirection name. The redirection name is used when launching sessions. When you launch a session, you are redirected to an OVD App Server using the redirection name as target host. In some cases the default redirection name is not valid. For instance, if you set up a private IP address and you want to connect to your OVD App Server from the internet. Page 9

11 5 INSTALLING AN OVD WEB ACCESS (EG WEB.TEST.DEMO) The Inuvika OVD Web Access can be installed on any server you want. It is, of course, possible to install it on the same machine as the OVD Session Manager. In this example, we are using web.test.demo as the OVD Web Access address Install the package inuvika-ovd-web-access: # apt-get install inuvika-ovd-web-access The installer asks if you want to connect the OWA width an existing OSM. The answer depends on whether you want to use this OWA in a specific Inuvika OVD farm or if you want a generic OWA. If you answered yes for the previous question, you now have to provide the host/ip address of the OSM. In our example: sm.test.demo. Using you web browser, go to you should see a login page: Page 10