INUVIKA OVD INSTALLING INUVIKA OVD ON RHEL 6 Mathieu SCHIRES Version: 0.96.1 Published January 19, 2015 http://www.inuvika.com
Contents 1 Prerequisites: RHEL 6 3 1.1 System Requirements................................... 3 1.2 SELinux............................................ 3 2 Repository 4 3 OVD Session Manager Installation and Configuration 5 3.1 Installing MySQL...................................... 5 3.2 Package Installation.................................... 5 3.2.1 Configuration.................................... 6 3.2.2 Setting Up the Subsystem Archive........................ 6 3.2.3 PHP Settings..................................... 7 4 Installing the OVD Application Server and OVD File Server (using Subsystem) 8 4.1 Setting a Redirection Name................................ 8 5 Installing an OVD Web Access (eg web.test.demo) 9 Page 1
The purpose of this document is to describe how the different server roles of Inuvika OVD can be installed on RHEL 6 system. Page 2
1 PREREQUISITES: RHEL 6 All operation have to be done as super user (root). 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 OWA 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 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. 1.2 SELINUX Inuvika OVD is not compatible width SELinux yet. So, if you have SELinux installed and enabled on your system, you have to disable it. To disable SELinux: Edit the /etc/selinux/config file and set the SELINUX variable to disabled. SELINUX=disabled Reboot your system # reboot Check SELinux is now disabled # sestatus SELinux status: disabled Page 3
2 REPOSITORY RHEL 6 uses the RPM packaging system. An Internet connection that provides HTTP access is required on your RHEL 6 system and add an Inuvika RPM repository into your system. The first step is to configure yum to enable the Inuvika rpm repository. Create the file /etc/yum.repos.d/ovd.repo width: [ovd-0.96.1] name=inuvika OVD 0.96.1 baseurl=http://archive.inuvika.com/ovd/0.96/rhel6/ enabled=1 gpgcheck=1 gpgkey=http://archive.inuvika.com/ovd/0.96/keyring Page 4
3 OVD SESSION MANAGER INSTALLATION AND CONFIGURATION The OSM is a LAMP (Linux Apache MySQL PHP) system. 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 package: # yum install mysql mysql-server To start automatically MySQL when the system boots up # chkconfig mysqld on Start the service # service mysqld start Define the root mysql password # mysqladmin -u root password 'mysql_root_password' 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: # yum install inuvika-ovd-session-manager inuvika-ovd-administration-\ console Launch the configuration tool # ovd-session-manager-config Admin login: admin Password: Retype password: Chroot download url [http://archive.inuvika.com/ovd/0.96/ovd-subsystem.tar\.gz]: Chroot destination [/var/cache/ovd/session-manager/ovd-subsystem.tar.gz]: Options: * chroot download: yes * chroot URI: http://archive.inuvika.com/ovd/0.96/ovd-subsystem.tar.\ gz * chroot directory: /var/cache/ovd/session-manager/ovd-subsystem.tar.gz Is this correct? [Y/n] Page 5
If you don t have access to Internet, please use the following command instead of the previous one: # ovd-session-manager-config --no-download Then, please read this to manually get the subsystem archive. Launch the Administration Console configuration tool # ovd-administration-console-config Session Manager address [127.0.0.1]: Configure and start apache service # chkconfig httpd on # service httpd restart 3.2.1 CONFIGURATION The first step is to go to http://sm.test.demo/ovd/admin 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: Database Type: MySQL Database host address: 127.0.0.1 Database username: root Database password: [root_password] Database name: ovd Table prefix: ovd_ 3.2.2 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 6
3.2.3 PHP SETTINGS You have to set the timezone setting located in the php configuration file. Edit the php configuration file # vi /etc/php.ini Change the setting width your own value (values can be found here http://php.net/manual/- en/timezones.php) date.timezone = Europe/Paris Restart the Apache server # service httpd restart Page 7
4 INSTALLING THE OVD APPLICATION SERVER AND OVD FILE SERVER (USING SUBSYSTEM) Install the package inuvika-ovd-subsystem: # yum install inuvika-ovd-subsystem Due to a conflict, you may have to uninstall samba packages before installing the inuvika-ovd-session-manager package. Remove the samba client and server packages: # yum remove samba* Launch the configuration tool # ovd-subsystem-config Session Manager address : sm.test.demo Chroot destination [/opt/ovd-subsystem]: If you are going to install an OAS on the same machine as your OSM, it is recommended to use 127.0.0.1 as the host. Configure and start the ovd-subsystem service # chkconfig ovd-subsystem on # service ovd-subsystem restart Your server should appear in the Unregistered server page. 4.1 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 127.0.0.1 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 8
5 INSTALLING AN OVD WEB ACCESS (EG WEB.TEST.DEMO) The OWA can be installed on any server you want. It is, of course, possible to install it on the same machine as the OSM. In this example, we are using web.test.demo as the OWA address Install the package inuvika-ovd-web-access: # yum install inuvika-ovd-web-access inuvika-ovd-web-access-ajaxplorer \ inuvika-ovd-guacamole The HTML5 client is enabled by installing inuvika-ovd-guacamole package. By default, it s based on using Tomcat 6 server Launch the configuration tool # ovd-web-access-config Do you want to link the OVD Web Access to a specific OVD Session Manager?\ ([yes]/no): Session Manager address [127.0.0.1]: sm.test.demo Configure and start apache service # chkconfig httpd on # service httpd restart Configure and start tomcat 6 service # chkconfig tomcat6 on # service tomcat6 restart Configure and start guacd service # chkconfig guacd on # service guacd restart Using you web browser, go to http://web.test.demo/ovd/, you should see a login page: Page 9